Re: FYI backport notes.texi from HEAD
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 - 1.3
+++ doc/Makefile.am 29 Jan 2008 03:50:32 -
@@ -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 - 1.134.2.26
+++ doc/libtool.texi 29 Jan 2008 03:50:34 -
@@ -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] respecti
Re: FYI backport notes.texi from HEAD
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? -- Tim RiceMultitalents(707) 887-1469 [EMAIL PROTECTED]
Re: FYI backport notes.texi from HEAD
Ralf Wildenhues wrote: > * Peter O'Gorman wrote on Thu, Jan 24, 2008 at 05:49:17PM CET: >> Tim Rice wrote: >>> On Thu, 24 Jan 2008, Ralf Wildenhues wrote: Guess that makes the section in README obsolete. Wanna kill it or replace it with a pointer to notes.texi? >>> Keep in mind not all systems have texinfo installed. >>> Although duplication is a pain to keep in sync. >> 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. sigh - I do not really care. I will revert the README changes later on today if people think that is best. Peter -- Peter O'Gorman http://pogma.com
Re: FYI backport notes.texi from HEAD
* Peter O'Gorman wrote on Thu, Jan 24, 2008 at 05:49:17PM CET: > Tim Rice wrote: > > On Thu, 24 Jan 2008, Ralf Wildenhues wrote: > >> Guess that makes the section in README obsolete. Wanna kill it > >> or replace it with a pointer to notes.texi? > > > > Keep in mind not all systems have texinfo installed. > > Although duplication is a pain to keep in sync. > > 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. Cheers, Ralf
Re: FYI backport notes.texi from HEAD
Tim Rice wrote: > On Thu, 24 Jan 2008, 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? > > Keep in mind not all systems have texinfo installed. > Although duplication is a pain to keep in sync. > 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. Peter -- Peter O'Gorman http://pogma.com
Re: FYI backport notes.texi from HEAD
On Thu, 24 Jan 2008, 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? Keep in mind not all systems have texinfo installed. Although duplication is a pain to keep in sync. -- Tim RiceMultitalents(707) 887-1469 [EMAIL PROTECTED]
Re: FYI backport notes.texi from HEAD
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 - 1.1220.2.488
+++ ChangeLog 24 Jan 2008 16:09:04 -
@@ -1,5 +1,10 @@
2008-01-24 Peter O'Gorman <[EMAIL PROTECTED]>
+ * doc/libtool.texi: Fixup Notes.
+ * README: Delete notes.
+
+2008-01-24 Peter O'Gorman <[EMAIL PROTECTED]>
+
* 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 - 1.17.2.6
+++ README 24 Jan 2008 16:09:04 -
@@ -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 - 1.134.2.25
+++ doc/libtool.texi 24 Jan 2008 16:09:07 -
@@ -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.
+
[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.
@@ -1870,23 +1876,24 @@
$CONFIG_SHELL ./configure [...]
@end ex
Re: FYI backport notes.texi from HEAD
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?
> 2008-01-24 Peter O'Gorman <[EMAIL PROTECTED]>
>
> * doc/libtool/texi: Backport notes.texi from HEAD.
> --- doc/libtool.texi 30 Nov 2007 04:19:20 - 1.134.2.24
> +++ doc/libtool.texi 24 Jan 2008 07:16:21 -
> +
> [EMAIL PROTECTED]
> +For C++ code with templates, it may be necessary to specify the way the
> compiler
> +will generate the instantiations. For Portland pgCC version5, use
> [EMAIL PROTECTED]'pgCC --one_instantiation_per_object'} and avoid parallel
> @command{make}.
Erm, C++ code with templates won't fare all that well with branch-1-5,
you may just want to delete this paragraph.
Thanks,
Ralf
FYI backport notes.texi from HEAD
I applied this to branch-1-5.
Peter
--
Peter O'Gorman
http://pogma.com
2008-01-24 Peter O'Gorman <[EMAIL PROTECTED]>
* doc/libtool/texi: Backport notes.texi from HEAD.
Index: doc/libtool.texi
===
RCS file: /sources/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.134.2.24
diff -u -r1.134.2.24 libtool.texi
--- doc/libtool.texi 30 Nov 2007 04:19:20 - 1.134.2.24
+++ doc/libtool.texi 24 Jan 2008 07:16:21 -
@@ -137,6 +137,7 @@
Configuring libtool
* AC_PROG_LIBTOOL:: Configuring @code{libtool} in @file{configure.in}.
+* Configure notes:: Platform-specific notes for configuration.
Including libtool in your package
@@ -1632,6 +1633,7 @@
@menu
* AC_PROG_LIBTOOL:: Configuring @code{libtool} in @file{configure.in}.
+* Configure notes:: Platform-specific notes for configuration.
@end menu
@node AC_PROG_LIBTOOL
@@ -1840,6 +1842,91 @@
@code{aclocal}. This may lead to weird errors when versions don't
match.
+
[EMAIL PROTECTED] Configure notes
[EMAIL PROTECTED] 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.
+
[EMAIL PROTECTED]
+
[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]
+For C++ code with templates, it may be necessary to specify the way the compiler
+will generate the instantiations. For Portland pgCC version5, use
[EMAIL PROTECTED]'pgCC --one_instantiation_per_object'} and avoid parallel @command{make}.
+
[EMAIL PROTECTED]
+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.
+
[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]
+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
