Re: FYI backport notes.texi from HEAD

[Peter O'Gorman]

Ralf Wildenhues wrote:
> Hi Peter,
> 
> * Peter O'Gorman wrote on Thu, Jan 24, 2008 at 08:29:08AM CET:
>> I applied this to branch-1-5.
> 
> Guess that makes the section in README obsolete.  Wanna kill it
> or replace it with a pointer to notes.texi?

> Erm, C++ code with templates won't fare all that well with branch-1-5,
> you may just want to delete this paragraph.

Doh!

Thanks.

I applied this.

Peter
-- 
Peter O'Gorman
http://pogma.com

Index: ChangeLog
===================================================================
RCS file: /sources/libtool/libtool/ChangeLog,v
retrieving revision 1.1220.2.488
diff -u -r1.1220.2.488 ChangeLog
--- ChangeLog   24 Jan 2008 07:27:40 -0000      1.1220.2.488
+++ ChangeLog   24 Jan 2008 16:09:04 -0000
@@ -1,5 +1,10 @@
 2008-01-24  Peter O'Gorman  <address@hidden>
 
+       * doc/libtool.texi: Fixup Notes.
+       * README: Delete notes.
+
+2008-01-24  Peter O'Gorman  <address@hidden>
+
        * doc/libtool/texi: Backport notes.texi from HEAD.
 
        * libtool.m4 (sys_lib_search_path_spec, sys_lib_dlsearch_path_spec):
Index: README
===================================================================
RCS file: /sources/libtool/libtool/README,v
retrieving revision 1.17.2.6
diff -u -r1.17.2.6 README
--- README      14 Jan 2008 21:34:50 -0000      1.17.2.6
+++ README      24 Jan 2008 16:09:04 -0000
@@ -83,62 +83,3 @@
 
 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 [...]
Index: doc/libtool.texi
===================================================================
RCS file: /sources/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.134.2.25
diff -u -r1.134.2.25 libtool.texi
--- doc/libtool.texi    24 Jan 2008 07:27:41 -0000      1.134.2.25
+++ doc/libtool.texi    24 Jan 2008 16:09:07 -0000
@@ -1853,6 +1853,12 @@
 @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.
+
address@hidden
 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 address@hidden  In case of doubt use @code{LDFLAGS=-Wl,-brtl} for 
the latter style.
@@ -1870,23 +1876,24 @@
 $CONFIG_SHELL ./configure [...]
 @end example
 
address@hidden
-For C++ code with templates, it may be necessary to specify the way the 
compiler
-will generate the instantiations.  For Portland pgCC version5, use
address@hidden'pgCC --one_instantiation_per_object'} and avoid parallel 
@command{make}.
-
address@hidden
-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
address@hidden
+  configure CC='gcc -m32'
address@hidden example
+rather than
address@hidden
+  configure CC=gcc CFLAGS=-m32 LDFLAGS=-m32
address@hidden example
+might help with this Libtool release.
+
address@hidden
 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.
@@ -1923,7 +1930,7 @@
 libtool's guesses at @command{configure} time by setting the
 @command{autoconf} cache variables
 @code{lt_cv_sys_lib_search_path_spec} and
address@hidden respectively to the correct search
address@hidden respectively to the correct search
 paths.
 
 @end itemize