I couldn't help noticing that Gtk reported: configure: error: Package requirements (glib-2.0 >= 2.35.3 ... but, to satisfy Atk, you appear to have installed glib-2.34.0!I have also found it necessary to set both LD_LIBRARY_PATH and PKG_CONFIG_PATH.
When using autogen.sh I have also found that some packages need ACLOCAL_PATH or something equivalent in ACLOCAL_FLAGS. For the tarball release, configure is (surely) supplied so I would advise not attempting to regenerate it - that being the point of autogen.sh.
For building Gtk and various supporting packages from Git source (where autogen.sh must be used) I use the attached script. This extracts whatever HEAD points to in each Git repo and builds in a temporary location, accumulating the required environment variables. The script is intended to be stepped through one block at a time as it doesn't really have any fault handling. Given the way it works, it may be useful/instructive even if not building from tarballs. (Of course, any feedback would be welcome!)
14/09/13 04:19, Fan Chun-wei wrote:
於 2013/9/14 上午 02:28, Mack J. Jenkins 提到:checking for GLIB - version >= 2.31.2... no configure: error: *** GLIB 2.31.2 or better is required. The latest version of *** GLIB is always available from ftp://ftp.gtk.org/. If GLIB is installed *** but not in the same location as pkg-config add the location of the file *** glib-2.0.pc to the environment variable PKG_CONFIG_PATH.Hi Mack, I might not be the best one to answer this, but this is what I normally do when I package tarballs under Linux to be able to test the code in Windows: -set the LD_LIBRARY_PATH to where you installed your own GLib build .so's, such as: export LD_LIBRARY_PATH=/opt/gnome.build.unstable/lib:/opt/gnome.build.unstable/lib64:$LD_LIBRARY_PATH -set the PKG_CONFIG_PATH to where you installed your own GLib build .pc files, such as: export PKG_CONFIG_PATH=/opt/gnome.build.unstable/lib/pkgconfig:/opt/gnome.build.unstable/lib64/pkgconfig:$PKG_CONFIG_PATH -Then attempt to do the autogen.sh/configure -> make -> make install dance one by one. It probably depends on your distro whether it uses a */lib64/ for 64-bit installations of the code you build (it does so on Fedora 18/19, for at least harfbuzz which is required for Pango on Linux). Hope this may be of help. With blessings. _______________________________________________ gtk-list mailing list gtk-list gnome org https://mail.gnome.org/mailman/listinfo/gtk-list
Attachment:
BUILD-GTK
Description: Text document