gtk keeps finding the wrong version of glib

slzckboy · 09-26-2005, 08:31 AM

ok when i try and run ./configure for gtk

its saying

Code:

** 'pkg-config --modversion glib-2.0' returned 2.6.6, but GLIB (2.4.1)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files

I have uninstalled 2.4.1 and then ran ldconfig but still no joy.

I've never quite got my head around the library enviroment variables etc so a little advise would be appreicated.
thnks

lanmanners · 09-27-2005, 01:52 AM

Looks ilke something wrong with the /usr/lib/pkgconfig/glib-2.0.pc file. Try uninstalling all version of glib and reinstall the latest/one you want.

LM

slzckboy · 09-27-2005, 04:31 AM

hi.

unfortunately I have already tried that . i removed all glib relatedpackages from /var/log/packages ad then went back to my distribution cd and did upgradepkg --install-new which will basically upgrade existing and install any ones that are missing.Still no joy.

I think it maybe an issue with library paths etc,but i'm not sure how to fix it.

sundialsvcs · 09-27-2005, 09:13 AM

Okay, then you might have to step a little-bit away from "package land" to diagnose this problem.

(1) Type: set | grep LD to see if the environment-variable LD_LIBRARY_PATH is defined. Linux will consult this to see where library-files are.

(2) Type: less /etc/ld.so.conf. This is a list of directories, in addition to /usr/lib, /lib, where libraries can be found.

(3) Type: locate libc.so to see where the files such as the one you seek actually are. (If necessary, as root, run nice /sbin/updatedb & .. notice the "&" .. to launch the locate-database update program in the background to make that information up-to-date. You can log-off root once you've launched it.)

This should be enough information to let you resolve the problem. The way that I'm reading it so-far, there are two possibilities. One is that the wrong version of libc is installed; the other is that the package database is wrong and needs to be rebuilt. I'm basically exploring the first possibility.

slzckboy · 09-27-2005, 10:48 AM

ok

echo LD_LIBRARY_PATH and set | grep LD both return thin air.
(i never new about the set command!!! thats a useful one!!)

cat /etc/ld/so.conf

/usr/local/lib/
usr/X11R6/LIB/
/usr/i486-slackware-linux/lib
/opt/kde/lib
/usr/lib/qt/lib
/usr/lib
/lib

libc.so is in /usr/lib and there is a libc.so.6 in /lib directory.

updatedb is ran nightly from a cron job but I have ran the command anyway a couple o times durig the time of me trying to resolve this.

wot do u think?

cheers

lanmanners · 10-21-2005, 08:26 AM

slzckboy, Can you check out the files /usr/include/glib (which is a symlink to glib-2.0)

If you have multiple versions, then that could be our problem.