Re: As of version 2.4, libtool provides support for dlopened modules

[Ralf Wildenhues]

Hello Roumen,

thanks for the bug report.

* Roumen Petrov wrote on Sun, Sep 26, 2010 at 08:41:54PM CEST:
> The email subject is quote of current libtool documentation - see
> for reference 
> http://www.gnu.org/software/libtool/manual/html_node/Dlopened-modules.html#Dlopened-modules
> .
> 
> Please, to update reference to the first libtool version that
> support dlopen.

The correct answer would be 0.9g, released sometime 1997.
I don't think this version information is relevant in any way.
Instead, let's just remove the version reference.
I'm pushing the following.

Cheers,
Ralf

    docs: do not refer to Libtool version with dlopen functionality.
    
    * doc/libtool.texi (Dlopened modules): Remove broken reference
    to what should have been Libtool 0.9g.
    Report by Roumen Petrov.

diff --git a/doc/libtool.texi b/doc/libtool.texi
index 56852ca..cd5a181 100644
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -3312,11 +3312,11 @@ interpreted language.  In fact, dlopen calls are 
frequently used in
 language interpreters to provide an efficient way to extend the
 language.
 
-As of version @value{VERSION}, libtool provides support for dlopened
-modules.  However, you should indicate that your package is willing to
-use such support, by using the @code{LT_INIT} option @samp{dlopen} in
address@hidden  If this option is not given, libtool will assume
-no dlopening mechanism is available, and will try to simulate it.
+Libtool provides support for dlopened modules.  However, you should
+indicate that your package is willing to use such support, by using the
address@hidden option @samp{dlopen} in @file{configure.ac}.  If this
+option is not given, libtool will assume no dlopening mechanism is
+available, and will try to simulate it.
 
 This chapter discusses how you as a dlopen application developer might
 use libtool to generate dlopen-accessible modules.