Re: gtk compiling woes

[Raja R Harinath <harinath cs umn edu>]

"Robert M. Fuhrer" <rmf@asgard.cs.columbia.edu> writes:
> > > 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).
> 
> Oops, I think you got that backwards - note the line that reads
> 
> > > make[2]: *** [gtkhscrollbar.lo] Error 1
> 
> identifying the shared-object (-fPIC) file as the culprit.

Nope.  `make' prints the name of the rule that failed.  The rule that
builds `gtkhscrollbar.lo' also builds `gtkhscrollbar.o' as a side
effect.  In fact, come to think of it, this may be a libtool problem,
since the `exit 1' is probably in `libtool'.  

- 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