* doc/libtool.texi: Fixup Notes.

* README: Delete notes.

diff --git a/ChangeLog b/ChangeLog
index e2d36e0c823c505edde2eb89007e24e9c37ae809..07997244285424d4ac6337b2004e11ef2a33dcec 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2008-01-24  Peter O'Gorman  <peter@pogma.com>
+
+       * doc/libtool.texi: Fixup Notes.
+       * README: Delete notes.
+
 2008-01-24  Peter O'Gorman  <peter@pogma.com>
 
        * doc/libtool/texi: Backport notes.texi from HEAD.

diff --git a/README b/README
index 28e235ced65f82a885212f1e08e5b155f92e520c..bc54995f399af702fe6bfd7365112965c06c6a50 100644 (file)
--- a/README
+++ b/README
@@ -83,62 +83,3 @@ test output like this:
 
 Alternatively, because each test is a shell script, in a non VPATH build,
 you can simply execute the tests, they will be verbose.
-
-Notes
-=====
-
-1)  Some HP-UX 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 sed (such as GNU sed) on
-these systems.
-
-2)  The vendor-distributed NCR MP-RAS cc programs emits copyright
-on standard error that confuse tests on size of conftest.err.  The
-workaround is to specify CC when run configure with CC='cc -Hnocopyr'.
-
-3)  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.
-
-4)  On Reliant Unix libtool has only been tested with the Siemens C-compiler
-and an old version of gcc provided by Marco Walther.
-
-5)  libtool.m4, ltdl.m4 and the configure.ac files are marked to use
-autoconf-mode, which is distributed with GNU Emacs 21, Autoconf itself, and 
-all recent releases of XEmacs. 
-
-6)  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.
-
-7)  Note in some cases you might need to put ABI-changing compiler flags
-into the compiler name.  For example, use of
-  configure CC='gcc -m32'
-rather than
-  configure CC=gcc CFLAGS=-m32 LDFLAGS=-m32
-might help with this Libtool release.  This will be fixed in Libtool-2.0.
-
-8)  Note that use of libltdl and a native dlopening mechanism for the
-same module within one program is not supported.  This includes modules
-loaded through inter-module dependencies.
-
-9)  Note that newer Sun Studio Fortran compilers might need Autoconf macros
-not yet present in 2.59 but only in CVS Autoconf.
-
-10) 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 http://lists.gnu.org/archive/html/libtool/2005-08/msg00088.html for
-more information.
-
-11) 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 `LDFLAGS=-Wl,-brtl'
-for the latter style.
-
-12) 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 `AR=/usr/bin/ar LD=/usr/bin/ld NM="/usr/bin/nm -B"'.
-
-13) On AIX, the `/bin/sh' is very slow due to its inefficient handling
-of here-documents.  A modern shell is preferable:
-  CONFIG_SHELL=/bin/bash; export $CONFIG_SHELL
-  $CONFIG_SHELL ./configure [...]

diff --git a/doc/libtool.texi b/doc/libtool.texi
index 24be2c6e8d933a6f808c3736ff8564e9b4d84d02..ff4181980a75af57ac902f41ebdf93072a66efd6 100644 (file)
--- a/doc/libtool.texi
+++ b/doc/libtool.texi
@@ -1852,6 +1852,12 @@ or a libtoolized package.
 
 @itemize
 
+@item
+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.
+
 @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,
@@ -1870,22 +1876,23 @@ CONFIG_SHELL=/bin/bash; export $CONFIG_SHELL
 $CONFIG_SHELL ./configure [...]
 @end example
 
-@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
-On Darwin, for C++ code with templates you need two level shared libraries.
-Libtool builds these by default if @env{MACOSX_DEPLOYMENT_TARGET} is set to
-10.3 or later at @command{configure} time.  See @url{rdar://problem/4135857}
-for more information on this issue.
-
 @c @item
 @c FreeBSD @command{make} does not conform to @sc{posix} in its handling
 @c of file modification times, which causes it to loop while building libtool.
 @c Consider using a different @command{such} as GNU make instead.
 
+@item
+Note in some cases you might need to put ABI-changing compiler flags
+into the compiler name.  For example, use of
+@example
+  configure CC='gcc -m32'
+@end example
+rather than
+@example
+  configure CC=gcc CFLAGS=-m32 LDFLAGS=-m32
+@end example
+might help with this Libtool release.
+
 @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
@@ -1923,7 +1930,7 @@ and dynamic linker search by default. If this occurs, you may override
 libtool's guesses at @command{configure} time by setting the
 @command{autoconf} cache variables
 @code{lt_cv_sys_lib_search_path_spec} and
-@code{lt_sys_lib_dlsearch_path_spec} respectively to the correct search
+@code{lt_cv_sys_lib_dlsearch_path_spec} respectively to the correct search
 paths.
 
 @end itemize