Re: failure "gnome libs" -current AMD64; 2/2/05 snapshot system

["Ian F. Darwin" <ian_(_at_)_darwinsys_(_dot_)_com>]

> Bah. The insane GNOME build environment is discarding compile warning
> and error messages, how useful!
>
> Could you try changing directory to the place where it failed, and
> manually running the failing cc invocation without the
>  ">/dev/null 2>&1" at the end?
>
> > cc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I./.. -DNEED_GNOMESUPPORT_H
> > -I../support -I../support -I/usr/local/include
> > -I/usr/local/include/glib-1.2 -I/usr/local/include/orbit-1.0
> > -I/usr/local/include -I/usr/local/include -I/usr/local/include/gtk-1.2
> > -I/usr/local/include/glib-1.2 -I/usr/X11R6/include -I/usr/local/include
> > -I/usr/X11R6/include -DGNOMEBINDIR=/usr/local/bin
> > -DGNOMESYSCONFDIR=\"/etc\" -DVERSION=\"1.4.2\" -I/usr/local/include
> > -I/usr/local/include/libpng -I/usr/local/include/gtk-1.2
> > -I/usr/local/include/glib-1.2 -I/usr/X11R6/include -O2 -pipe -Wall
> > -Wunused -c Table-stubs.c -o Table-stubs.o >/dev/null 2>&1
Paugh! I've seen this before, though. This is one of two ways to deal 
with code that is so poorly written that you can't see the "make" lines 
hidden between all the warning messages from the compiler... It's the 
easy way, but it's not the right way.

And people run this stuff in production? *Sigh*.