Welcome

Troves being gleaned while surfing on the Internet mostly about computer/IT/system skills and tricks, Welcome here ...
Powered By Blogger

Disclaimer

This blog is written by the owner with real practices and tests and intended to hold all original posts except there is a clear declaration for referencing from others. Thanks for tagging with the source link or other tips for reference from here if you would like to quote partial or full text from posts in this blog.

Tuesday, December 28, 2010

Ordeal with Installation of GTK+-2.4 in Linux Enviroment ( Fedora 13 & x86 64bit )

1.
go ftp://ftp.gtk.org/pub/gtk/v2.4/ :

wget ftp://ftp.gtk.org/pub/gtk/v2.4/glib-2.4.7.tar.bz2

bunzip glib-2.4.7.tar.bz2 && tar xvf   glib-2.4.7.tar.bz2

cd glib-2.4.7.tar.bz2 && ./configure && make && make install


pkg-config  --modversion  glib-2.0
2.4.7

2.
wget ftp://ftp.gtk.org/pub/gtk/v2.4/pango-1.4.1.tar.bz2

same steps to install pango 1.4.1 as above


but, OOPS:

*** 'pkg-config --modversion glib-2.0' returned 2.4.7, 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.4.0 or better is required. The latest version of
*** Glib is always available from ftp://ftp.gtk.org/.

Even clean up all other occurrences of glib-2.0 as directories and keep only one, the problem is adamant !


since I installed glib2.26.1 before, so I tried with "cd glib2.26.1 && make uninstall", seems effective a bit!

*** 'pkg-config --modversion glib-2.0' returned 2.4.7, but GLIB (2.27.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.4.0 or better is required. The latest version of
*** Glib is always available from ftp://ftp.gtk.org/.

actually I have also installed ever glib2.27.4 before 2.26.1.........., it appears every building installation leaves certain trash or something somewhere!

So, follow the same trick : cd glib2.27.4 && make uninstall

Gosh, not that lucky again! just the same gnats!


Desperately, find / -name "*glib-2.0*"  -delete !! (a bit of daunting admittedly.. but might it be worth taking risk)


Then get back to glib2.4.7 and "
make clean &&
make uninstall &&
./configure
make
make install

still no joy :

checking for GLIB - version >= 2.4.0... no
*** Could not run GLIB test program, checking why...
*** The test program compiled, but did not run. This usually means
*** that the run-time linker is not finding GLIB or finding the wrong
*** version of GLIB. If it is not finding GLIB, you'll need to set your
*** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point
*** to the installed location  Also, make sure you have run ldconfig if that
*** is required on your system
***
*** If you have an old version installed, it is best to remove it, although
*** you may also be able to get things to work by modifying LD_LIBRARY_PATH
configure: error:
*** Glib 2.4.0 or better is required. The latest version of
*** Glib is always available from ftp://ftp.gtk.org/.

--------------------- how GLIBC and GTK (or merely this pango?) makes bitter stuff ---------------------------------------


Now it sounds that the version retrieved by ./configure (of pango) as the number in " but GLIB (2.27.4)...." stems from dynamic library libglib-2.0.so (if it is a symblic link, then its target).

Following this clue, try to place correct version of .so (that produced by glibc-2.4.7, say) into where the "pkg-config --libs glib-2.0" tells !



It is weird however, that the .so glib2.4.7 produces is always WRONG! even make many other dependant like yum disabled!


Continuously, also tried with glib2.4.8 forwardly and glib2.4.1 backwardly, both having the same problem --- producing dynamic libraries (.so) that is not recognizable by all its dependants that I  know.

succumbed to this nasty for now! 

------------------------------ Follow up----------------------------------------

=>Later,  tried with even much higher version - GLib 2.9.6, nothing better in the end!

=>Later still, count on the latest version of GTK+ 2.91 up to Dec 22, 2010, it got, incredibly blocked by:
...
Requested 'glib-2.0 >= 2.27.5' but version of GLib is 2.9.6
...

this is awfully another buffoon which is out of my expectation:
should 2.9.6 be a lower version than 2.27.5?
is it reasonable? why...

--- maybe only the GTK+ developer can tell the secret.

No comments: