Re: GTK+ 1.2.7: failing to compile gtkmain.c

[Raja R Harinath <harinath cs umn edu>]

Tim Janik <timj@gtk.org> writes:
> On 17 Feb 2000, Raja R Harinath wrote:
> > > gcc -DHAVE_CONFIG_H -I. -I../../gtk
> > > -I.. -DG_LOG_DOMAIN=\"Gtk\" -DGTK_DISABLE_COMPAT_H
> > > -DGTK_EXE_PREFIX=\"/usr/local\" -DGTK_DATA_PREFIX=\"/usr/local\" -DGTK_SYSCONFDIR=\"/usr/local/etc\" -DGTK_LOCALEDIR=\"/usr/local/share/locale\" -I../.. -DGTK_NO_CHECK_CASTS
> > > -DUSE_XIM -I/usr/local/lib/glib/include -I/usr/local/include
> > > -D_REENTRANT -I/usr/X11R6/include -g -O2 -Wall -c
> > > ../../gtk/gtkmain.c -o gtkmain.o >/dev/null 2>&1
> >    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> > This looks like a compiler error.  It compiles the -fPIC version but
> > not the non-PIC version... wierd.  Maybe you temporarily ran out of
> 
> it's libtool's responsiveness to pas -fPIC to the compiler, so this looks
> more like a libtool bug, rather than a gcc one.

Maybe.  However, in the snipped out part of the log, gtkmain was
compiled to .libs/gtkmain.lo -- and that is the PIC version.  That
compiled fine.  Now, the build probably had both --enable-static and
--enable-shared.  So, libtool also builds a gtkmain.o non-PIC.  The
build is breaking there.  In the "both static and shared" mode,
'libtool' silences the compiler output for the non-PIC part, to cut
down on duplicate messages from the compiler.  However, in the case of
a crash in the non-PIC part, we don't have any compiler output to look
at.  We can get an explicit non-PIC build with unsilenced compiler
output by running

        make gtkmain.o

- 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