Proper way to replace Glib; need to build GTK3.0 for Anjuta 3.0

spaceboy909 · 05-14-2011, 04:21 PM

Hi all. I've gone about as far as I can with this without trashing my system. I'm running Mint 10 LXDE with XFCE.

Ultimate objective: Install latest Anjuta 3.0 from source (not yet in repos)

Anjuta ./configure reported a need for updated packages, such as GTK 3.0, Glib, Gio, etc.

I downloaded GTK 3.0 and 'config' reported a need for an updated Glib. So I downloaded that and have installed it successfully (no prefixes; from home dir.)

But now GTK config is stating that it has found two versions of Glib, which I guess makes sense since I made no attempt to replace the old one.

So, what is/was the proper way to replace the old Glib so there is only one version, or, is that a bad idea? Will some software still be dependent on the old Glib, or do the devs make the libraries backward compatible? Where do I go from here?

Quote:

checking for GLIB - version >= 2.28.0...
*** 'pkg-config --modversion glib-2.0' returned 2.28.6, but GLIB (2.26.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.28.0 or better is required. The latest version of
*** GLIB is always available from ftp://ftp.gtk.org/pub/gtk/.

andrewthomas · 05-14-2011, 07:27 PM

You are facing an uphill battle. You do need to remove the newer version of glib.

Your best bet would be to use the GNOME Jhbuild tool to build a gtk-3.0 enviornment at an alternate prefix ( either in your home directory or somewhere in /opt, such as /opt/gnome )

http://live.gnome.org/Jhbuild

You are probably going to have to build one of the following modulesets

Code:

http://git.gnome.org/browse/jhbuild/plain/modulesets/gnome-apps-3.2.modules
http://git.gnome.org/browse/jhbuild/tree/modulesets/gnome-apps-3.0.modules

RockDoctor · 05-14-2011, 07:31 PM

Quote:

Originally Posted by spaceboy909

So, what is/was the proper way to replace the old Glib so there is only one version, or, is that a bad idea? Will some software still be dependent on the old Glib, or do the devs make the libraries backward compatible? Where do I go from here?

Normally, installing a new version removes the old version. Are you sure one isn't 32-bit and the other 64-bit?
I'd try removing the old version - if the removal software doesn't object, it's not likely to break anything. If there's an objection, I'd definitely reconsider.

spaceboy909 · 05-15-2011, 07:12 PM

Thanks for the tips guys, but it seems I'm getting in over my head on this, and this is not a necessity.

I think I'll just stick with my current version of Anjuta, and hopefully, Mint 11 will have GTK 3.0 support.