Re: Error building GObject in glib-1.3.5

[Owen Taylor <otaylor redhat com>]

Eric Lemings <elemings lemings com> writes:

> Eric Lemings wrote:
> 
> > FYI:
> >
> > [elemings cyberia glib-1.3.5]$ ./configure --enable-maintainer-mode
> > --enable-debug=yes --enable-threads --disable-nls --enable-msg-prefix
> > ...
> > [elemings cyberia glib-1.3.5]$ make
> > ...
> > make  all-recursive
> > make[1]: Entering directory `/usr/local/src/redhat/BUILD/glib-1.3.5'
> > Making all in .
> > make[2]: Entering directory `/usr/local/src/redhat/BUILD/glib-1.3.5'
> > make[2]: Leaving directory `/usr/local/src/redhat/BUILD/glib-1.3.5'
> > Making all in gobject
> > make[2]: Entering directory
> > `/usr/local/src/redhat/BUILD/glib-1.3.5/gobject'
> > ...
> > /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall -D_REENTRANT  -o
> > glib-mkenums
> > gcc -g -O2 -Wall -D_REENTRANT -o glib-mkenums
> > gcc: No input files
> > make[2]: *** [glib-mkenums] Error 1
> > make[2]: Leaving directory
> > `/usr/local/src/redhat/BUILD/glib-1.3.5/gobject'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/usr/local/src/redhat/BUILD/glib-1.3.5'
> > make: *** [all-recursive-am] Error 2
> > [elemings cyberia glib-1.3.5]$
> 
> I wonder...do you guys do 'make distcheck' before making releases or do
> you just use the force?  ;)

We use make distcheck.

And I built the tarballs from scratch on a clean machine.

And even with your configure options, I have no trouble building
GLib.

So...


The build rules for glib-mkenums are admittedly rather screwed up
looking at them (glib-mkenums should be in bin_SCRIPTS, not
bin_PROGRAMS.) So it probably has something to with your versions of
Make or something like that.

Regards,
                                        Owen