+2005-04-04 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
+
+ * notes.texi: Platform-specific configuration notes.
+ * doc/libtool.texi: Include as section.
+ * bootstrap, doc/Makefile.am: build also as notes.txt and distribute.
+
2005-04-04 Gary V. Vaughan <gary@gnu.org>
Under certain circumstances, not all of the macro files were
: ${FGREP=fgrep}
: ${SED=sed}
: ${LN_S='ln -s'}
+: ${MAKEINFO=makeinfo}
test -f ./configure.ac || {
echo "bootstrap: can't find ./configure.ac, please rerun from top_srcdir"
# Whip up some dirty Makefiles:
makefiles=
-for dirty in ./Makefile ./tests/Makefile
+for dirty in ./Makefile ./tests/Makefile ./doc/Makefile
do
test -f $dirty || {
makefiles="$makefiles $dirty"
$MAKE ./testsuite AUTOTEST="$AUTOM4TE --language=autotest" \
srcdir=. top_srcdir=.. PACKAGE="$2" VERSION="$3"
cd ..
+ cd doc
+ $MAKE notes.txt srcdir=. top_srcdir=.. MAKEINFO="${MAKEINFO}"
+ cd ..
}
test -f clcommit.m4sh && $MAKE -f Makefile.maint commit \
Configuring libtool
* LT_INIT:: Configuring @code{libtool} in @file{configure.ac}.
+* Configure notes:: Platform-specific notes for configuration.
Including libtool in your package
@menu
* LT_INIT:: Configuring @code{libtool} in @file{configure.ac}.
+* Configure notes:: Platform-specific notes for configuration.
@end menu
@node LT_INIT
@end example
+@node Configure notes
+@subsection Platform-specific configuration notes
+
+While Libtool tries to hide as many platform-specific features as possible,
+some have to be taken into account when configuring either the Libtool package
+or a libtoolized package.
+
+@include notes.texi
+
+
@node Distributing
@section Including libtool in your package
--- /dev/null
+@itemize
+
+@item
+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 ELF@. In case of doubt use @code{LDFLAGS=-Wl,-brtl} for the latter style.
+
+@item
+For C++ code with templates, it may be necessary to specify the way the compiler
+will generate the instantiations. For Portland pgCC version5, use
+@code{CXX='pgCC --one_instantiation_per_object'} and avoid parallel @command{make}.
+
+@item
+FreeBSD @command{make} does not conform to @sc{posix} in its handling
+of file modification times, which causes it to loop while building libtool.
+Consider using a different @command{such} as GNU make instead.
+
+@item
+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.
+
+@item
+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.
+
+@item
+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
+@code{CC='cc -Hnocopyr'}.
+
+@item
+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.
+
+@item
+On Reliant Unix libtool has only been tested with the Siemens C-compiler
+and an old version of @command{gcc} provided by Marco Walther.
+
+@item
+@file{libtool.m4}, @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.
+
+@end itemize