GIMP complains about glib

Ephracis · 01-14-2005, 12:25 AM

I am trying to install gimp and first it complain about not having a new enough version of glib. So I downloaded the newest and did the usual configure/make/make install. Now I get this from configure for gimp:

Code:

checking for GLIB - version >= 2.4.5... 
*** 'pkg-config --modversion glib-2.0' returned 2.6.1, but GLIB (2.4.2)
*** 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 would gladly remove the old version of glib but how can I remove it? I guess it was installed with slackware.

dr_zayus69 · 01-14-2005, 01:42 AM

i could be wrong but if it came with the distro then maybe it came as a rpm. Do rpm -qa | grep glib and if you see the old version you can get rid of it with rpm -e glib.

__J · 01-14-2005, 04:31 AM

slackware does not use rpm's. MezzyMeat if you want to see the packages currently installed on your system do the following in a terminal:

cd /var/log/packages
ls | more

if you want to remove one, do the following as root:

removepkg <package>

Now me personally, I wouldn't download a new glib and ./configure, make, and make install even if I removed the old library first. I've always had an easier time administering what I do and don't have on the system. So I personally would configure the new glib (after I uninstalled the old one) with:

./configure --prefix=/usr
make

and I use checkinstall for all my installations to make life easier when you want to remove/upgrade something (you can find it on a slackware mirror in the /extra directory).
These are just my preferences though and do things whatever way you feel most comfortable with.

p.s. -- when you install something with ./configure,make,make install (thus installing into /usr/local) when there is an conflicting version in /usr, it will always pick up /usr instead of /usr/local first (unless you modify all the corresponding paths the configure script is looking for).