Re: libtool 1.6

[Ralf Wildenhues]

* Bob Friesenhahn wrote on Sat, Nov 20, 2004 at 08:44:53PM CET:
> The libtool 2.0 documentation still refers to libtool 1.6, which never 
> existed.

Easily fixed.  The very paragraph this is in has some more stuff in it
which is still debated right now (resp. needs clarification).

Regards,
Ralf

Index: doc/libtool.texi
===================================================================
RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.183
diff -u -r1.183 libtool.texi
--- doc/libtool.texi    19 Nov 2004 11:33:26 -0000      1.183
+++ doc/libtool.texi    22 Nov 2004 11:19:19 -0000
@@ -2077,13 +2078,13 @@
 @file{configure.ac}, rendering the call out to the generated libtool
 script obsolete.
 
-Starting with libtool 1.6, the multipass generation of the libtool
+Starting with libtool 2.0, the multipass generation of the libtool
 script has been consolidated into a single @file{config.status} pass,
 which happens after all the code in @file{configure.ac} has
 completed.  The implication of this is that the libtool script does
 not exist during execution of code from @file{configure.ac}, and so
 obviously it cannot be called for @samp{--config} details anymore.  If
-you are upgrading projects that used this idiom to libtool 1.6 or
+you are upgrading projects that used this idiom to libtool 2.0 or
 newer, you should replace those calls with direct references to the
 equivalent Autoconf shell variables that are set by the configure time
 tests before being passed to @file{config.status} for inclusion in the