From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Sat Jan 09 1999 - 05:20:18 EST
On Jan 9, 1999, Godmar Back <gback@marker.cs.utah.edu> wrote:
> Ah. I bet I need gmake. (Although I'm sure that's not desired either
> and probably a bug too.)
Yep, you need gmake in the developer Makefiles, for automatic
dependency tracking. The `Makefile.in's generated with `make dist',
however, don't required GNU make, and include the dependencies
generated by the developer.
> Also, I noticed that there's now two invocations of gcc per files.
You may --disable-static at configure-time, if you prefer. I had
thought of making this the default, but later I decided not to do it
yet.
> Is it doing this because it needs to extract libtool information?
Nope, that's only so that libtool can create a static (non-PIC) and a
shared (PIC) version of the code.
> Let us know when you have a fixed version in CVS that we can test.
It should be working by now.
BTW, if you don't feel like updating autoconf and automake by now, you
can get your build to proceed by running:
gmake AUTOCONF="./missing autoconf" AUTOMAKE="./missing automake" \
ACLOCAL="./missing aclocal" AUTOHEADER="./missing autoheader"
But I'd first get the original version of any autoconf-related file,
since the missing script will just touch any file that seems to be
out-of-date.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:33 EDT