Upgrading GTK

GT_Onizuka · 07-09-2004, 11:33 PM

Okay, I was trying to install a Genesis emulator, when it complained that my version of GTK was out-of-date.

Code:

*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GTK+ is incorrectly installed.
configure: error: *** GTK+ version 2.4.0 not found!

I figure, okay, this shouldn't be too hard, so I head over to GTK's website, and download the latest version, 2.4.3. I stumble across another error. During configure:

Code:

checking for glib-2.0 >= 2.4.0    atk >= 1.0.1    pango >= 1.4.0... Requested 'glib-2.0 >= 2.4.0' but version of GLib is 2.2.3

configure: error: Library requirements (glib-2.0 >= 2.4.0    atk >= 1.0.1    pango >= 1.4.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them.

Okay, a little dependency hell, I can deal, so I download the latest version of GLib, 2.4.1. Configure and make go fine, I do my good old checkinstall, everything seems to check out A-OK. But when I go to try and install GTK again, I get the same error message. I check on my computer, and I also have dated versions of Pango and ATK. Okay okay, more stuff to install, but no worries, it'll all work out in the end. According to the site, I need to install in the order: GLib, Pango, ATK, then GTK+. So I try installing Pango, after I have installed GLib, and this is the message I get.

Code:

*** Could not run GLIB test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GLIB is incorrectly installed.
configure: error:
*** Glib 2.4.0 or better is required. The latest version of
*** Glib is always available from ftp://ftp.gtk.org/.

Grrr.... Okay, so maybe I needed to upgrade GLib, since I definitely already had it on my computer (since its a required thing for GTK etc. etc.). I try upgrading it (all goes well)

Code:

Package glib-1.2.10-i386-2 upgraded with new package ./glib-2.4.4-i386-1.tgz.

But I still get the same errors AND it looks like my current programs aren't recognizing the new stuff. Programs that use GTK won't launch anymore, for example, when I try and launch XMMS:

Code:

ynadji@onizuka:ynadji$ xmms
xmms: error while loading shared libraries: libgmodule-1.2.so.0: cannot open shared object file: No such file or directory

Well that's no good, so I reinstall the version of GLib that was on my Slackware CD, and now I'm back to square one. Is there an easier way to upgrade ALL of GTK? Slapt-Get doesn't have any new packages, and upgrading GTK seems to be a pain in the ass unless I'm missing something TOTALLY blatantly obvious.

Thanks for the help

.

mrgrieves · 07-10-2004, 01:46 AM

don't do it. GTK 2.4 is full of bugs. Whats more, You'll have to upgrade the programs that use GTK.

Its also incompatible with wxPython.

Andrew Benton · 07-10-2004, 06:08 AM

Gtk 2.4 is not full of bugs, but I have to agree, don't do it unless you really want to learn how to compile from the source. That's the reason I'd do it. Xmms broke because you uninstalled gtk-1.2 which is a completly different thing to gtk-2.4. But yes, things will break if you install gtk-2.4 over the gtk-2.2 that comes with Slack-9.1.

GT_Onizuka · 07-10-2004, 09:01 AM

Okay, I don't have a problem compiling from source, pretty much everything I do install, is compiled from source, I just use Checkinstall and install them as packages, so they're easier to remove. Thanks for explaining the whole, "breaking of applications" thing, but I'm still wondering why Pango wasn't able to detect the new install of GLib I just did. I imagine, sometime down the road, I would need to upgrade GTK.

Andrew Benton · 07-10-2004, 11:53 AM

I've never used Checkinstall, I always do it by hand. Where did Checkinstall install glib-2.4?

GT_Onizuka · 07-10-2004, 02:18 PM

Wherever it was specified from ./configure, so, the default location. If it makes any difference, I also tried installing it with 'make install' and I ended up with the same problem.