Re: gtk compiling woes

[Raja R Harinath <harinath cs umn edu>]

Rasmus Tamstorf <rt@brandx.net> writes:
> Despite reading (and trying to follow) all the FAQ's and HOWTO's about
> building from the CVS tree I can't get past the gtk package :-(
> 
> If I do a './autogen.sh --prefix=/usr/local/gnome' in the gtk directory
> (updated today) I get :
> 
>   aclocal: configure.in: 178: macro `AM_PATH_GLIB' not found in library

This is explained in the FAQ ("Do I have to do anything special if I'm
not installing in /usr or /usr/local?" or something like that).
 
> Since AM_PATH_GLIB is defined in glib.m4, I can get past this error by
> doing a 'export ACLOCAL_FLAGS=../glib' BUT is that really the right way of
> doing it ? Shouldn't the configuration be set up to pick up any required
> m4 files from the glib package ?

The glib `make install' places `glib.m4' where it thinks aclocal will
find it.  You'll have to set ACLOCAL_FLAGS if that expectation is wrong.

> gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\"Gtk\" -I.. -I../../glib
> -I/usr/X11R6/include -g -O2 -DGTK_NO_CHECK_CASTS -Wall -DUSE_XIM
> -Wp,-MD,.deps/gtkhscrollbar.p -c -fPIC -DPIC gtkhscrollbar.c
> mv -f gtkhscrollbar.o gtkhscrollbar.lo
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -DG_LOG_DOMAIN=\"Gtk\" -I.. -I../../glib
> -I/usr/X11R6/include -g -O2 -DGTK_NO_CHECK_CASTS -Wall -DUSE_XIM
> -Wp,-MD,.deps/gtkhscrollbar.p -c gtkhscrollbar.c >/dev/null 2>&1
> make[2]: *** [gtkhscrollbar.lo] Error 1
> make[2]: Leaving directory `/usr/src/gnome/gtk+/gtk'

That's interesting: the shareable object (-fPIC) got created without
complaint.  The static object compilation exited, however.  The error
messages are helpfully discarded, which is usually the right thing to
do, but not in this case (AFAIK, on x86 machines, -fPIC should be the
one that causes problems).

Anyway, first, check if your disk is full or something like that.

If you have no such problem, try doing

	make distclean
	rm -f config.cache		# just to be sure
	configure --disable-shared

And try compiling again.  You should be able to see the error messages
in this case, _if_ the compilation fails.

HTH
- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash