Hello Stefan,
* Stefan Sperling wrote on Wed, Nov 28, 2007 at 05:13:39PM CET:
>
> the "Using libtool" section in the manual starts talking about
> a "wrapper script" in one paragraph without explaining beforehand
> what that script is.
[...]
> The following patch simply reverts the order of those two
> paragraphs to fix this.
Thanks. Applied to HEAD and branch-1-5. The online manual will be
fixed automatically when the next release appears.
Cheers,
Ralf
2007-11-30 Stefan Sperling <[EMAIL PROTECTED]> (tiny change)
* doc/libtool.texi (Linking executables): Reorder paragraphs.
Index: doc/libtool.texi
===================================================================
RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.232
diff -u -r1.232 libtool.texi
--- doc/libtool.texi 16 Nov 2007 07:08:33 -0000 1.232
+++ doc/libtool.texi 30 Nov 2007 04:17:56 -0000
@@ -785,18 +785,17 @@
Note that libtool added the necessary run-time path flag, as well as
@option{-lm}, the library libhello.la depended upon. Nice, huh?
-Since libtool created a wrapper script, you should use libtool to
-install it and debug it too. However, since the program does not depend
-on any uninstalled libtool library, it is probably usable even without
-the wrapper script.
-
-
@cindex wrapper scripts for programs
@cindex program wrapper scripts
Notice that the executable, @code{hell}, was actually created in the
@[EMAIL PROTECTED] subdirectory. Then, a wrapper script was created
in the current directory.
+Since libtool created a wrapper script, you should use libtool to
+install it and debug it too. However, since the program does not depend
+on any uninstalled libtool library, it is probably usable even without
+the wrapper script.
+
On NetBSD 1.2, libtool encodes the installation directory of
@file{libhello}, by using the @samp{-R/usr/local/lib} compiler flag.
Then, the wrapper script guarantees that the executable finds the
_______________________________________________
http://lists.gnu.org/mailman/listinfo/libtool
