+2010-09-26 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ 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.
+
2010-09-23 Peter Rosin <peda@lysator.liu.se>
msvc: don't try to export import descriptors.
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
-@file{configure.ac}. 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
+@code{LT_INIT} 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.