Re: "Can't link to Pango"

[Bric <bric flight us>]

On 02/13/2014 12:53 PM, Emmanuele Bassi wrote:
> hi;
>
> On 13 February 2014 17:37, Bric <bric flight us> wrote:
>
> > I did the above workaround, successfully, and got past my pango snag....
> >
> > Then ./configure complained about not having atk-bridge; i went down that
> > chain of dependencies, with at-spi2-core, etc., (some of the latest git
> > failed to "make"; i used version releases), and made gtk+ ./configure happy.
> > But gtk+ make is now failing — HANGING (not exiting!) on an error:
> > (glib-compile-resources:6887): GLib-GObject-CRITICAL **:
> > /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to call
> > g_type_init()
> you're building against a far too old version of GLib. check your
> LD_LIBRARY_PATH, because it seems the configure script is catching a
> version of GLib recent enough to satisfy the dependency check, but the
> linker is trying to use the system version of GLib.

Yes, it's a mess. Here is even more of the mess:  When I try to build 
latest gtk+ from git, it complains that it is finding glib 2.39.4, but 
that the minimum it wants is 2.39.5.

glib 2.39.5 is not an official release yet (correct me if I'm wrong), 
so, I make the assumption that, at the moment, glib 2.39.5 means glib 
git. So, I update and build my glib from git successfully (just a few 
minutes ago), and install.  So, you think gtk+ ./configure is now happy 
?  No! It gives me this weirdness:

------------------ begin quote ------------------------------
checking for HP-UX... no
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.39.5...
*** 'pkg-config --modversion glib-2.0' returned 2.39.5, but GLIB (2.39.4)
*** 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.39.5 or better is required. The latest version of
*** GLIB is always available from ftp://ftp.gtk.org/pub/gtk/.

-------------- end quote ---------------------

Is this because the "git" version doesn't definitively dominate all the 
version markers when it installs, and leaves behind the previously 
installed versions ??  (git gtk+ is picking up the previous 
"glib-2.39.4", somehow, the one compiled from release tarball.)


> > This is a never ending battle, this gtk+ on my Ubuntu 10.10, with the
> > sprawling tree and extensive chains of dependencies, each of which is not
> > yielding easily (!!!) — battling over 48 hours now...
> you're trying to build a very recent version of a complex library on a
> 4 years old distribution: issues are to be expected, as well as some
> pain in rebuilding the entire stack.

"roger" on that

> why are you targeting such an old platform?

Well... i guess it all started with the advent of "unity", in Ubuntu 
11.  I was one of those happy Ubuntu/Gnome users who started kicking and 
screaming, bewildered why a good thing, such as Ubuntu as we had known 
it up until Maverick, was suddenly and irrevocably taken away.  I have 
held on to Maverick all these years, beyond its official expiration date 
(miraculously, it has been unofficially supported all this time, and 
continued to be stable enough for a production environment). Maybe I've 
finally reached its limits, as one, well-lubricated, integrated whole.  
If I'm causing library confusion, there's no telling.  Perhaps I need to 
learn how to build proper debian packages, so I can add them to this 
system with all the proper triggers and cross-linking in play.

I /do/ remember building gtk+ many years ago, on fedora ... it feels 
like I'm going back in time right now :-))