Andrew,
Thanks for the reply. After trying what you said:
Quote:
Originally posted by Andrew Benton
PKG_CONFIG_PATH
Code:
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
|
I get the following after running ATk's configure:
checking for GLIB - version >= 2.5.7...
*** 'pkg-config --modversion glib-2.0' returned 2.8.0, but GLIB (2.2.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
no
configure: error:
*** GLIB 2.5.7 or better is required. The latest version of
*** GLIB is always available from
ftp://ftp.gtk.org/. If GLIB is installed
*** but not in the same location as pkg-config add the location of the file
*** glib-2.0.pc to the environment variable PKG_CONFIG_PATH.
So, I took a shot in the dark and tried:
Code:
cp /usr/local/lib/libglib-2.0.so.0.800.o /usr/lib/libglib-2.0.so.0.800.0
/sbin/ldconfig
Running /sbin/ldconfig -v indicated to me that /etc/ld.so.cache now recognized the 2.8.0 library as the valid target.
The result was, that Atk compiled and installed without errors. However I ran into a pretty nasty side effect. Specifically, Gnome stopped letting me run new things.. such as, I couldn't open new terminals or new windows of Firefox. When I rebooted, Gnome refused to even start. So I had to change to a text terminal, and undo the above cp command, and re-run ldconfig to undo the damage I apparently did. I re-did and un-did all of the above several times to confirm that indeed my above commands were causing this problem. Are the contents of /usr/lib actually dynamically linked libraries, so to speak?
Anyway, I undid the cp/ldconfig business and went ahead and re-tried to install Atk, since I'm assuming it wouldn't exactly be installed properly any more. Sure enough, configure yielded the same message as at the top.
Pango, strangely, "configure"ed ok, but elicited compiler errors after running "make" in regards to ftglue.c. More on that later, this post is crowded enough as it is.
so, new questions for my newbie education:
1. Can someone confirm to me what was happening?
2. The first, original, above message indicates that ldconfig still points /etc/ld.so.cache to the glib 2.2.1 library, in /usr/lib, even though the PKG_CONFIG_PATH can force pkgconfig to recognize that 2.8.0 is present in /usr/local/lib. How do I properly uninstall 2.2.1, and get ldconfig to find 2.8.0 without manually cp'ing it to /usr/lib (or is that necessary anyway)?
3. Assuming I do uninstall 2.2.1 and get 2.8.0 running, will Gnome take to it? After all, when I tried my above bastardized approach, Gnome seemed to have problems.
4. As a workaround: If I do a bastardized copy of the 2.8.0 library into /usr/lib and run ldconfig, then compile & install atk, then remove the 2.8.0 library from /usr/lib, will atk or other dependent software work in the future?
Thanks again for the help!