David Necas (Yeti) wrote:
On Sat, Mar 25, 2006 at 07:28:06PM -0600, Jim Sabatke wrote:what does "ldd /path/to/gimp" say?jim ripley:~/programs/gimp/libs/gtk+-2.8.16> ldd /opt/gnome/bin/gimp ... libgobject-2.0.so.0 => /usr/local/lib/libgobject-2.0.so.0 (0x40544000) libgmodule-2.0.so.0 => /usr/local/lib/libgmodule-2.0.so.0 (0x4057b000) libglib-2.0.so.0 => /opt/gnome/lib/libglib-2.0.so.0 (0x40582000)Well, obviously not everything is right with your GLib installation when you have part of it in /opt/gnome and part in /usr/local/lib. I suppose one of them is the old version that causes troubles. Yeti -- That's enough.
Yes, you are correct. I checked /usr/local/lib and found that the following files were there:
/usr/local/lib/libgobject-2.0.la /usr/local/lib/libgobject-2.0.so /usr/local/lib/libgobject-2.0.so.0 /usr/local/lib/libgobject-2.0.so.0.400.5They were the only files from any glib install, so I'm a bit confused as to how they got there. I know once or twice I've forgotten the "prefix=/opt/gnome" and had to do a "make uninstall" and rerun "./configure" I don't know if the "make uninstall" was broken, or if I had errors that stopped the process.
What I do know is that my system works now and I'm very happy about that. Thanks, Jim