On Thursday 25 September 2003 07:58, Ricardo Wagemaker wrote:
checking for pkg-config... /usr/local/bin/pkg-config checking for GLIB - version >= 2.2.0... *** 'pkg-config --modversion glib-2.0' returned 2.2.1, but GLIB (2.0.6) *** 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 no configure: error: Test for GLIB failed. See the file 'INSTALL' for help.
Anyone in here got any idea where glib leaves or where and how I can remove the old version of it?
I had a very similar problem yesterday. - Find where your glib 2.0.6 is. It is probably in /usr/lib. - Copy your updated glib to the same directory. Perhaps your updated glib is in /usr/local/lib, if you compiled it from sources, like I have just done. (We are copying the full name libraries, and not dealing with the symlinks) - As root, run ldconfig. If you run like "ldconfig -v | grep glib", you should see the symlink updated by ldconfig. Now pkg-config should not be able to find the old glib anymore and should not complain. The problem is that it complains even if the correct library is going to be loaded anyway, since /usr/local/lib is scanned before /usr/lib (as in /etc/ld.config.conf).