I'm just a newbie myself, but let me try to quickly address this since I have recently been messing with the same problem. furthermore, in many message boards, numerous other newbies have experienced this exact same problem and their pleas often go un-answered. I actually saw your post while searching for the replies to my original one a few days ago.
(in case it may be helpful to you, search for a threat titled "Quest to install gxine (and learn something too)" or some such similar title)
with much thanks to Andrew, what i ended up doing is setting the following global variables:
Code:
PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
LDFLAGS=-L/usr/local/lib
CPPFLAGS=-I/usr/local/include
LD_CONFIG_PATH=/usr/local/lib
export PKG_CONFIG_PATH LDFLAGS CPPFLAGS LD_CONFIG_PATH
yours may have to change according to your particular setup.
then I ran /usr/ldconfig just for good measure, and voila the next ./configure attempt worked.
in the grand tradition of newbie-ism, i tried much that did NOT work:
1. copying the new glib-2.0.so.0.800.0 library into /usr/lib then running ldconfig (this just messed up everything else that used glib-2.0.so.0.200.1)
2. uninstalling the old version of glib via rpm (apparently did nothing)
3. moving the glib-2.0.pc file around (the PKG_CONFIG_PATH is all you need)
The bottom line, as far as I could figure, is that the glib installation process put the files under the /usr/local branch of the file structure, but pkg-config won't look there unless you set it's global variable. (poke around good in /usr/local/lib/pkgconfig, and you'll see what i mean) the other 3 flags then direct the next configure script you run to use the glib libraries that you just recently installed. (as opposed to any that came installed with your distribution, which it pkg-config can't find anyway.) if you forget to set the last three variables, or maybe just the last one, I bet you'll see something like this: pkg_config reports that the new version of glib 2.9 is installed, but the library in use is an old one like 2.2.1. do some research on ld.so.conf if you want to learn more why this is.
please let me know if this helps. (feel free to PM) working on this was a great learning experience, though in the long run i may just have confused myself more.