When starting the new gimp-1.2.3, I get the following error message
(it seems to be a non-fatal error; gimp looks like it is running
OK, but anyway..):
dyld: /sw/lib/gimp/1.2/plug-ins/Lighting can't open library:
/sw/lib/libgck-1.2.2.dylib (No such file or directory, errno = 2)
LibGimp-WARNING **: gimp-real: wire_read: unexpected EOF
dyld: /sw/lib/gimp/1.2/plug-ins/MapObject can't open library:
/sw/lib/libgck-1.2.2.dylib (No such file or directory, errno = 2)
otool -L shows that indeed MapObject and Lighting do have a
dependency on
/sw/lib/libgck-1.2.2.dylib (compatibility version 3.0.0,
current version 3.0.0)
although the library that is installed with gimp1.2.3-1 is
/sw/lib/libgck-1.2.0.dylib (compatibility version 1.0.0,
current version 1.3.0)
Explanation: libgck-1.2.2.dylib came with gimp-1.2.2-6 which was
installed while the new gimp was compiled. Apparently during
compilation, the libraries in /sw/lib are loaded before the
libraries in the build directory. I would consider this a bug in
the makefiles, because the binaries then depend on libraries that
happened to be there at compile time and not on those present at
runtime. In the case of gimp, this gives an error, because the
"new" library has a lower compatibility version number than the
"old" one.
--
Martin
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users
