Tim Rice wrote:
> On Thu, 24 Jan 2008, Ralf Wildenhues wrote:
>
>>> It will also be in the libtool manual on www.gnu.org (which the README
>>> is not), so I am not really worried about that.
>> At least with Libtool HEAD, there is a notes.txt generated from
>> notes.texi.
>
> Excelent!
>
> Difficult to do in branch-1-5?
>
Done.
Peter
--
Peter O'Gorman
http://pogma.com
2008-01-29 Peter O'Gorman <[EMAIL PROTECTED]>
* doc/Makefile.am, doc/notes.texi, doc/libtool.texi: Move the
platform specific notes to notes.texi and generate notes.txt.
Reported by Tim Rice
Index: doc/Makefile.am
===================================================================
RCS file: /sources/libtool/libtool/doc/Attic/Makefile.am,v
retrieving revision 1.3
diff -u -r1.3 Makefile.am
--- doc/Makefile.am 8 Apr 2001 00:29:06 -0000 1.3
+++ doc/Makefile.am 29 Jan 2008 03:50:32 -0000
@@ -2,4 +2,12 @@
AUTOMAKE_OPTIONS = gnits
info_TEXINFOS = libtool.texi
-libtool_TEXINFOS = PLATFORMS fdl.texi
+libtool_TEXINFOS = PLATFORMS fdl.texi notes.texi
+EXTRA_DIST = notes.txt
+
+all-local: $(srcdir)/notes.txt
+
+$(srcdir)/notes.txt: notes.texi
+ cd $(srcdir) && \
+ $(MAKEINFO) --no-headers $(MAKEINFOFLAGS) -o notes.txt notes.texi
+
Index: doc/libtool.texi
===================================================================
RCS file: /sources/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.134.2.26
diff -u -r1.134.2.26 libtool.texi
--- doc/libtool.texi 24 Jan 2008 16:12:19 -0000 1.134.2.26
+++ doc/libtool.texi 29 Jan 2008 03:50:34 -0000
@@ -1850,90 +1850,8 @@
some have to be taken into account when configuring either the Libtool package
or a libtoolized package.
[EMAIL PROTECTED]
[EMAIL PROTECTED] notes.texi
[EMAIL PROTECTED]
-Note that Sun C++ compiler versions before 5.6 may need some special
-setup to link properly against shared versions of the C++ standard libraries.
-See @url{http://lists.gnu.org/archive/html/libtool/2005-08/msg00088.html} for
-more information.
-
[EMAIL PROTECTED]
-On AIX there are two different styles of shared linking, one in which symbols
-are bound at link-time and one in which symbols are bound at runtime only,
-similar to [EMAIL PROTECTED] In case of doubt use @code{LDFLAGS=-Wl,-brtl} for the latter style.
-
[EMAIL PROTECTED]
-On AIX, native tools are to be preferred over binutils; especially for C++ code,
-if using the AIX Toolbox GCC 4.0 and binutils, configure with
[EMAIL PROTECTED]/usr/bin/ar LD=/usr/bin/ld NM='/usr/bin/nm -B'}.
-
[EMAIL PROTECTED]
-On AIX, the @command{/bin/sh} is very slow due to its inefficient handling
-of here-documents. A modern shell is preferable:
[EMAIL PROTECTED]
-CONFIG_SHELL=/bin/bash; export $CONFIG_SHELL
-$CONFIG_SHELL ./configure [...]
[EMAIL PROTECTED] example
-
[EMAIL PROTECTED] @item
[EMAIL PROTECTED] FreeBSD @command{make} does not conform to @sc{posix} in its handling
[EMAIL PROTECTED] of file modification times, which causes it to loop while building libtool.
[EMAIL PROTECTED] Consider using a different @command{such} as GNU make instead.
-
[EMAIL PROTECTED]
-Note in some cases you might need to put ABI-changing compiler flags
-into the compiler name. For example, use of
[EMAIL PROTECTED]
- configure CC='gcc -m32'
[EMAIL PROTECTED] example
-rather than
[EMAIL PROTECTED]
- configure CC=gcc CFLAGS=-m32 LDFLAGS=-m32
[EMAIL PROTECTED] example
-might help with this Libtool release.
-
[EMAIL PROTECTED]
-The default shell on UNICOS 9, a ksh 88e variant, is too buggy to
-correctly execute the libtool script. Users are advised to install a
-modern shell such as GNU bash.
-
[EMAIL PROTECTED]
-Some HP-UX @command{sed} programs are horribly broken, and cannot handle
-libtool's requirements, so users may report unusual problems. There
-is no workaround except to install a working @command{sed} (such as GNU sed)
-on these systems.
-
[EMAIL PROTECTED]
-The vendor-distributed NCR MP-RAS @command{cc} programs emits copyright
-on standard error that confuse tests on size of @file{conftest.err}. The
-workaround is to specify @env{CC} when run configure with
[EMAIL PROTECTED]'cc -Hnocopyr'}.
-
[EMAIL PROTECTED]
-Any earlier DG/UX system with ELF executables, such as R3.10 or
-R4.10, is also likely to work, but hasn't been explicitly tested.
-
[EMAIL PROTECTED]
-On Reliant Unix libtool has only been tested with the Siemens C-compiler
-and an old version of @command{gcc} provided by Marco Walther.
-
[EMAIL PROTECTED]
[EMAIL PROTECTED], @file{ltdl.m4} and the @file{configure.ac} files are marked
-to use autoconf-mode, which is distributed with GNU Emacs 21, Autoconf itself,
-and all recent releases of XEmacs.
-
[EMAIL PROTECTED]
-When building on some linux systems for multilib targets
[EMAIL PROTECTED] sometimes guesses the wrong paths that the linker
-and dynamic linker search by default. If this occurs, you may override
-libtool's guesses at @command{configure} time by setting the
[EMAIL PROTECTED] cache variables
[EMAIL PROTECTED] and
[EMAIL PROTECTED] respectively to the correct search
-paths.
-
[EMAIL PROTECTED] itemize
@node Distributing
@section Including libtool in your package
Index: doc/notes.texi
===================================================================
RCS file: doc/notes.texi
diff -N doc/notes.texi
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ doc/notes.texi 29 Jan 2008 03:50:34 -0000
@@ -0,0 +1,84 @@
[EMAIL PROTECTED]
+
[EMAIL PROTECTED]
+Note that Sun C++ compiler versions before 5.6 may need some special
+setup to link properly against shared versions of the C++ standard libraries.
+See @url{http://lists.gnu.org/archive/html/libtool/2005-08/msg00088.html} for
+more information.
+
[EMAIL PROTECTED]
+On AIX there are two different styles of shared linking, one in which symbols
+are bound at link-time and one in which symbols are bound at runtime only,
+similar to [EMAIL PROTECTED] In case of doubt use @code{LDFLAGS=-Wl,-brtl} for the latter style.
+
[EMAIL PROTECTED]
+On AIX, native tools are to be preferred over binutils; especially for C++ code,
+if using the AIX Toolbox GCC 4.0 and binutils, configure with
[EMAIL PROTECTED]/usr/bin/ar LD=/usr/bin/ld NM='/usr/bin/nm -B'}.
+
[EMAIL PROTECTED]
+On AIX, the @command{/bin/sh} is very slow due to its inefficient handling
+of here-documents. A modern shell is preferable:
[EMAIL PROTECTED]
+CONFIG_SHELL=/bin/bash; export $CONFIG_SHELL
+$CONFIG_SHELL ./configure [...]
[EMAIL PROTECTED] example
+
[EMAIL PROTECTED] @item
[EMAIL PROTECTED] FreeBSD @command{make} does not conform to @sc{posix} in its handling
[EMAIL PROTECTED] of file modification times, which causes it to loop while building libtool.
[EMAIL PROTECTED] Consider using a different @command{such} as GNU make instead.
+
[EMAIL PROTECTED]
+Note in some cases you might need to put ABI-changing compiler flags
+into the compiler name. For example, use of
[EMAIL PROTECTED]
+ configure CC='gcc -m32'
[EMAIL PROTECTED] example
+rather than
[EMAIL PROTECTED]
+ configure CC=gcc CFLAGS=-m32 LDFLAGS=-m32
[EMAIL PROTECTED] example
+might help with this Libtool release.
+
[EMAIL PROTECTED]
+The default shell on UNICOS 9, a ksh 88e variant, is too buggy to
+correctly execute the libtool script. Users are advised to install a
+modern shell such as GNU bash.
+
[EMAIL PROTECTED]
+Some HP-UX @command{sed} programs are horribly broken, and cannot handle
+libtool's requirements, so users may report unusual problems. There
+is no workaround except to install a working @command{sed} (such as GNU sed)
+on these systems.
+
[EMAIL PROTECTED]
+The vendor-distributed NCR MP-RAS @command{cc} programs emits copyright
+on standard error that confuse tests on size of @file{conftest.err}. The
+workaround is to specify @env{CC} when run configure with
[EMAIL PROTECTED]'cc -Hnocopyr'}.
+
[EMAIL PROTECTED]
+Any earlier DG/UX system with ELF executables, such as R3.10 or
+R4.10, is also likely to work, but hasn't been explicitly tested.
+
[EMAIL PROTECTED]
+On Reliant Unix libtool has only been tested with the Siemens C-compiler
+and an old version of @command{gcc} provided by Marco Walther.
+
[EMAIL PROTECTED]
[EMAIL PROTECTED], @file{ltdl.m4} and the @file{configure.ac} files are marked
+to use autoconf-mode, which is distributed with GNU Emacs 21, Autoconf itself,
+and all recent releases of XEmacs.
+
[EMAIL PROTECTED]
+When building on some linux systems for multilib targets
[EMAIL PROTECTED] sometimes guesses the wrong paths that the linker
+and dynamic linker search by default. If this occurs, you may override
+libtool's guesses at @command{configure} time by setting the
[EMAIL PROTECTED] cache variables
[EMAIL PROTECTED] and
[EMAIL PROTECTED] respectively to the correct search
+paths.
+
[EMAIL PROTECTED] itemize
