What might cause this infinite recursion?

2004-11-20 Thread Bruce Korb 

Hi all,

This is new behavior with the latest released automake, and it happens
on Solaris but not Linux.  The "Makefile.in" produced causes Solaris
"make" to choke and GNU make to think it is happy but do the following:

> /bin/ksh ../libtool --mode=link /net/megami/opt/apps/forte62/SUNWspro/bin/cc  
> -xO4   -o autogen -export-dynamic  autogen-ag.o ../autoopts/libopts.la 
> -L/u/local/lib -lguile -lguile-ltdl -lcrypt -lsocket -lnsl -lm -lm 
> -Wl,-R/u/local/lib -lm -ldl -lgen
> mkdir .libs
> /net/megami/opt/apps/forte62/SUNWspro/bin/cc -xO4 -o .libs/autogen 
> autogen-ag.o -Wl,-R/u/local/lib  ../autoopts/.libs/libopts.so -L/u/local/lib 
> /u/local/lib/libguile.so /u/local/lib/libguile-ltdl.so -lcrypt -lsocket -lnsl 
> -lm -ldl -lgen -R/u/local/lib
> creating autogen
> gmake[4]: Entering directory `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> Making all in test
> gmake[5]: Entering directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[5]: Nothing to be done for `all'.
> gmake[5]: Leaving directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[5]: Entering directory `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> gmake[5]: Warning: File `autogen' has modification time 1.8 s in the future
> gmake[6]: Entering directory `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> Making all in test
> gmake[7]: Entering directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[7]: Nothing to be done for `all'.
> gmake[7]: Leaving directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[7]: Entering directory `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> gmake[7]: Warning: File `autogen' has modification time 1.4 s in the future
> gmake[8]: Entering directory `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> Making all in test
> gmake[9]: Entering directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[9]: Nothing to be done for `all'.
> gmake[9]: Leaving directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[9]: Entering directory `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> gmake[9]: Warning: File `autogen' has modification time 0.93 s in the future
> gmake[10]: Entering directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5'
> Making all in test
> gmake[11]: Entering directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'
> gmake[11]: Nothing to be done for `all'.
> gmake[11]: Leaving directory 
> `/home/bkorb/tools/ag/autogen-5.6.5pre6/=b/agen5/test'

This goes on until memory is exhausted or I break out of it.
The issue has to do with $(man_MANS).  If I remove "all-am"'s dependency
on $(MANS), the recursion stops.  The issue I am dealing with is that
my ``autogen.1'' is a derived file but cannot be derived until the
``autogen'' executable has been built, so there is a dependency.

Heres the "Makefile.am" source:

http://cvs.sourceforge.net/viewcvs.py/*checkout*/autogen/autogen/agen5/Makefile.am?rev=HEAD

Anyone have hints?  Should I go back to the previous Automake?
Thanks! - Bruce

Convincing Automake to support libtool

2004-11-20 Thread Bob Friesenhahn 
I am using Autoconf 2.59 and Automake 1.9.3.  I am trying to update my 
project to use the latest development libtool 2.0 (1.9h).  Libtool 2.0 
eliminates AC_PROG_LIBTOOL and uses LT_INIT instead.  My project is 
using Automake includes so each subdirectory has its own Makefile.am 
file which is included into the top Makefile.am file.

The problem I am having is that Automake is not detecting that I am 
using libtool.  It seems to depend on seeing AC_PROG_LIBTOOL in 
configure.ac.  Somehow it does detect that the libtool test suite 
is using libtool.  The test suite does not use Automake includes.

Automake is producing an error message like:
coders/Makefile.am:172: Libtool library used but `LIBTOOL' is undefined
coders/Makefile.am:172:
coders/Makefile.am:172: The usual way to define `LIBTOOL' is to add 
`AC_PROG_LIBTOOL'
coders/Makefile.am:172: to `configure.ac' and run `aclocal' and `autoconf' 
again.
What should I do in order to encourage Automake to believe that 
libtool is in use?

Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen

Re: Convincing Automake to support libtool

2004-11-20 Thread Bob Friesenhahn 
It seems that none of the libtool related macro definitions are being 
expanded in configure even though aclocal and autoconf do not produce 
any warnings.  I expect that this is why Automake does not detect 
libtool.

Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen

Re: Convincing Automake to support libtool

2004-11-20 Thread Bob Friesenhahn 
On Sat, 20 Nov 2004, Bob Friesenhahn wrote:
It seems that none of the libtool related macro definitions are being 
expanded in configure even though aclocal and autoconf do not produce any 
warnings.  I expect that this is why Automake does not detect libtool.
What I have now learned the hard way is that aclocal ignores the 
AC_CONFIG_MACRO_DIR([m4]) definition in configure.ac.  As a result it 
does not look for extra m4 files in the m4 subdirectory.  In order to 
bootstrap and obtain a working configure script I had to execute:

aclocal -I m4 && autoheader && autoconf && automake
It seems to me that this is a bug in aclocal.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED]
http://www.simplesystems.org/users/bfriesen