Got it! It was really a hard one to figure... and it was entirely my fault:
I installed glib and gtk 2.0 about one year ago, and, probably because I did not RTFM, I was unhappy to see that the installation procedure did not remove the 1.2 libraries. Of course, they are meant to coexist. Also, glib-config --version kept returning the 1.2 version, which bugged me (again, classic RTFM problem).
I don't remember exactly which was the app I was trying to install, but it wasn't seeing the new libraries (I probably did not run ldconfig); so, I had this great idea! I changed the softlink in /usr/local/lib/libglib-1.2.so.0.0.10 (or whatever minor version it was at the time) to point to the 2.0 library! Now, wasn't I smart? And guess what, the app worked! Ha!
Of course I ended up breaking lots of X stuff (oddly, the failing apps only complained about the undefined g_source_add function and many others kept working fine; are the 2.0 and 1.2 versions that similar?) and because I had done it very late at night and was very sleepy I couldn't remember what I had done (duh!).
I got to the matter now because I tried to install gtk 2.0 (which I had meanwhile uninstalled) and the glib test prog complained:
Code:
'glib-config --version' returned 1.2.10, but GLIB (2.8.5) was found!
Again, no one on the entire net seemed to have a similar problem; only conflicts between different installs of 1.2 versions of glib.
I double-checked that the lib paths pointed to the 1.2 install and concluded that the only way the prog could be getting the 2.8.5 version number was because a 2.0 lib had gotten misplaced or misnamed. But because I had fresh installed glib 1.2 that could not be the case. The only alternative: a stray symlink...
Hope this helps anyone, although it does require some lack of brains to do what I did!
Bye!