Re: config.status (or something) writes out a crippled libtool script

[Ralf Wildenhues]

Just for the record (so someone searching the archives won't be
mislead):

* Peter Ekberg wrote on Wed, Aug 24, 2005 at 03:40:42PM CEST:
> 
> I have autoconf and automake from cvs as of yesterday after the
> mail by Ralf saying that you need bleeding edge.

I did not say you needed bleeding edge for CVS HEAD Libtool.  What I
said is that, if you use CVS Autoconf, and that was last updated within
a certain time frame, then you need to update now.  (There is no reason
for the autotools to support each and every (un)patched state of
unreleased versions of the other autotools.)

When my proposed patch (on libtool-patches) of yesterday is applied, you
will be fine with either CVS HEAD versions of Autoconf/Automake, or
Autoconf 2.59, Automake 1.9.6.

(I encouraged upgrading Autoconf also because we fixed a couple of bugs
in Autotest. :-)

Cheers,
Ralf