New binary portability problem identified
Isn't Linux fun?
The problems with g_option_error_quark people are seeing is because both the static RPM and the autopackage were built against static versions of GTKmm 2.6, which introduces a silent dependency on Glib 2.6 even if only 2.4 level features are used.
The solution is to build the portable binaries against *mm 2.4 static libraries.
Aaron, can you rebuild the autopackage against *mm 2.4 static libraries and push a -2 release of the package, so users on GTK+ 2.4 systems can use them again?
thanks -mike
On 7/30/05, Mike Hearn <mike@...869...> wrote:
The solution is to build the portable binaries against *mm 2.4 static libraries.
Wow. Can someone please take care of closing all the bugs on this, and of making sure this fix is in 0.42.1?
bulia:
On 7/30/05, Mike Hearn <mike@...869...> wrote:
The solution is to build the portable binaries against *mm 2.4 static libraries.
Wow. Can someone please take care of closing all the bugs on this, and of making sure this fix is in 0.42.1?
1246201 is the only one open on this but I will not close it until the packages are actually available.
ralf
Mike Hearn wrote:
Aaron, can you rebuild the autopackage against *mm 2.4 static libraries and push a -2 release of the package, so users on GTK+ 2.4 systems can use them again?
Hey, is this one any better? I really don't know how to check.
http://inkscape.modevia.com/ap/inkscape-0.42-2.x86.package
Aaron Spike
participants (4)
-
unknown＠example.com -
bulia byak -
Mike Hearn -
Ralf Stephan