At 9:06 Uhr -0500 10.03.2002, Alexander Strange wrote: >On Sunday, March 10, 2002, at 07:29 AM, Max Horn wrote: >>libgck is now (back?) at 1.2.0. >It looks like the new one was buggy, so they downgraded.
OK >> However, since this lib is shipped as part of Gimp (now that I >>write it I vaguely remember having read something similiar on the >>list). It seems Gimp was linked against the *installed* version >>(which is incorrect), and not against the version it built. This is >>clearly a bug in the build process. Maybe we can fix it with an >>extension to our patch?\ >I'm already doing that; and being confused by the libtool options. >The fix would be somewhere in plug-ins/libgck/gck/Makefile ,but i >don't know libtool :) >> >> >>I am not sure what is causing the other warnings. >Looks like a bug in the Gimp. I get the same message with 1.2.2, BTW: Gimp-WARNING **: /sw/lib/gimp/1.2/modules/libcolorsel_gtk.so: module_init() symbol not found Gimp-WARNING **: /sw/lib/gimp/1.2/modules/libcolorsel_triangle.so: module_init() symbol not found Gimp-WARNING **: /sw/lib/gimp/1.2/modules/libcolorsel_water.so: module_init() symbol not found >> >>Another issue: the patch hardcodes "/sw" when invoking perl! This >>is not good. >It's okay; perl is disabled anyway :) A (partially broken) gimp-perl >package is on the tracker. Well, it's still incorrect, please fix it. Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:[EMAIL PROTECTED]> phone: (+49) 6151-494890 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
