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 i

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] htt

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 in

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/