Hello everyone,

I have recently started dabbling in the wonderful world of Linux, so I am by all means a newbie. I use mandrake 10.0, and love it so far. However, I am trying to install gtk 2.4.4, which requires pango, which requires glib 2.4+, and I'm running into some troubles. When trying to install pango 1.4.4, it says I need glib 2.4+. As far as I can tell, I have successfully installed glib 2.4.5. Is there any way I can verify that?

Thanks

First let me caution you on compiling apps for an rpm based distro. ( you didn't say that, but it sounded like maybe you did). Have you tried the the tool 'urpmi'? I would take a look there and see if that will help you. I'd check it myself but I don't have a mndk box - sorry.

yea generally systems keep both an old (glib gtk) and (gtk2 glib2)
so both the old apps and the new ones will run
i think it's cool you jump right in compiling gtk but it's kind of involved so i will do my best to explain
and it's going to take a while

*first when you install binary (rpm) version of libraries you also need -devel package
to compile programms against the lib

*second on your system are multiple directories called "pkgconfig"
my main one is in /usr/lib
when compiling packages installation directories are set in configure scripts with --prefix=
if you don't set --prefix= by default it's /usr/local then pkgconfig directory ends up in /usr/local/lib

in pkgconfig are lots of
*.pc (package config files)
mine has:
glib.pc
and
glib-2.0.pc
the names of these stay the same for all gtk and gtk2 versions

also there is a shell variable PKG_CONFIG_PATH
The default settings for PKG_CONFIG_PATH are
/lib/pkgconfig,
/usr/lib/pkgconfig and
/usr/local/lib/pkgconfig. These settings are hard- coded
and do not have to be exported with the additional paths
if you install stuff in for instance /opt/gtk2
you need to add that path to PKG_CONFIG_PATH in your /etc/bashrc or ~/.bashrc
all you need to know about these .pc files is
*configure scripts use them to determine the location of includes and libraries to write Makefiles*
use "man pkg-config" to see how to get info
these files can't conflict -- that is don't install gtk2 in /usr/local and another version in /opt/gtk2
(you can use PKG_CONFIG_PATH to controll what packages are used to compile things if you install things in strange places) this is what developers do as they work on new lib versions.

*third anytime you install a new library put its path in
/etc/ld.so.conf if the path isn't there already
then run as root
ldconfig

*fourth for libs just look in /usr/lib /usr/local/lib and like that to see whats there
and remember to compile against these libs their header *.h files need to be in
/usr/include /usr/local/include and like that and for binary (not compiled ) packages
these files are often in seperate developement packages

have fun (sorry about the length) i hope this is comprehensable

*update*

After a few days of tinkering around, I finally got it. Urpmi did the trick for me, thanks for the suggestion BigNate. Unfortunately, I didn't accomplish what I set out to do, which was getting a deeper understanding of the CLI and file system. In retrospect, I was probably biting off more than I could chew, but then again I'm the kind of guy that likes to jump in and get his hands dirty. On the bright side I learned a lot about urpmi