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 example
[EMAIL
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]
Autoreconf calling order order [WAS FYI: 333-gary-refactor-LTDL_INIT.patch]
Hi Eric, On 23 Jan 2008, at 22:00, Eric Blake wrote: The problem seems to stem from the fact that I had an older version of libltdl copied into my M4 tree, and autoreconf runs aclocal prior to libtoolize, so it was picking up the old definition of LTDL_INIT which conflicted with my new contents of configure.ac. I haven't picked through the logic inside autoreconf, but it seems completely wrong to me for it to run any tool that affects the contents of aclocal.m4 after aclocal itself (unless, perhaps, it reruns aclocal again later). From libtoolize.m4sh(func_scan_files): # Libtoolize affects the contents of aclocal.m4, and should be run before # aclocal, so we can't use configure --trace which relies on a consistent # configure.(ac|in) and aclocal.m4. I'm punting this one as an autoreconf bug. Cheers, Gary -- Gary V. Vaughan ([EMAIL PROTECTED]) PGP.sig Description: This is a digitally signed message part
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: Autoreconf calling order order [WAS FYI: 333-gary-refactor-LTDL_INIT.patch]
* Gary V. Vaughan wrote on Thu, Jan 24, 2008 at 06:19:37PM CET: I haven't picked through the logic inside autoreconf, but it seems completely wrong to me for it to run any tool that affects the contents of aclocal.m4 after aclocal itself (unless, perhaps, it reruns aclocal again later). aclocal will be rerun again after libtoolize. Cheers, Ralf
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: Autoreconf calling order order [WAS FYI: 333-gary-refactor-LTDL_INIT.patch]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 1/24/2008 11:00 AM: | * Gary V. Vaughan wrote on Thu, Jan 24, 2008 at 06:19:37PM CET: | I haven't picked through the logic inside autoreconf, but it seems | completely wrong to me for it to run any tool that affects the contents | of aclocal.m4 after aclocal itself (unless, perhaps, it reruns aclocal | again later). | | aclocal will be rerun again after libtoolize. But that didn't help in the (admittedly less common) case where there was an incompatible out-of-date libtool.m4 already incorporated in aclocal.m4 before the first aclocal run. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmN+P84KuGfSFAYARAtnYAKC+aJhZYOFtdkRhYOS0kbx+j+PkJACgnFfn hsbuxydqQO1zqN7cDrL022c= =l4sP -END PGP SIGNATURE-
Re: Autoreconf calling order order
* Eric Blake wrote on Thu, Jan 24, 2008 at 07:57:20PM CET: According to Ralf Wildenhues on 1/24/2008 11:00 AM: | * Gary V. Vaughan wrote on Thu, Jan 24, 2008 at 06:19:37PM CET: | I haven't picked through the logic inside autoreconf, but it seems | completely wrong to me for it to run any tool that affects the contents | of aclocal.m4 after aclocal itself (unless, perhaps, it reruns aclocal | again later). | | aclocal will be rerun again after libtoolize. But that didn't help in the (admittedly less common) case where there was an incompatible out-of-date libtool.m4 already incorporated in aclocal.m4 before the first aclocal run. Unless the previous libtool.m4 comes from a released version, I'm not sure I'm inclined to look more closely (and anyway I can't before Monday). Cheers, Ralf
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]
341-gary-libtoolize-recognise-LTDL_INIT
Okay to commit?
Index: ChangeLog
from Gary V. Vaughan [EMAIL PROTECTED]
* libtoolize.m4sh (Main): Copy (or link) libltdl sources
into project tree when LTDL_INIT was seen, whether or not
`--ltdl' is passed.
(func_check_macros): Recommend LTDL_INIT instead o
LT_WITH_LTDL when `--ltdl' is used before configure.ac is
upgraded.
* tests/libtoolize.at: Test that it works.
(_LT_AT_LTDL_SETUP): Factor out some common test setup.
Reported by Eric Blake [EMAIL PROTECTED]
Index: libtoolize.m4sh
===
RCS file: /sources/libtool/libtool/libtoolize.m4sh,v
retrieving revision 1.65
diff -u -u -r1.65 libtoolize.m4sh
--- libtoolize.m4sh 17 Jan 2008 05:36:21 - 1.65
+++ libtoolize.m4sh 25 Jan 2008 04:43:17 -
@@ -921,7 +921,7 @@
func_echo and rerunning libtoolize.
fi
elif test -z $m4dir; then
- if $opt_ltdl test ${ltdlprefix}m4 != $m4dir; then
+ if test ${ltdlprefix}m4 != $m4dir $seen_ltdl || $opt_ltdl; then
acmacrodir=${ltdlprefix}m4
else
acmacrodir=$aclocaldir
@@ -945,12 +945,16 @@
$seen_libtool ||
func_echo Remember to add \`LT_INIT' to $configure_ac.
-if $opt_ltdl; then
-
- # Suggest using LT_WITH_LTDL if appropriate:
- $seen_ltdl ||
-func_echo Consider adding \`LT_WITH_LTDL' to $configure_ac
+# Suggest using LTDL_INIT if appropriate:
+$opt_ltdl if test x$seen_ltdl != x:; then
+ case $ltdl_mode in
+ subproject) ltdl_init_args= ;;
+ *) ltdl_init_args=([$ltdl_mode]) ;;
+ esac
+ func_echo Remember to add \`LTDL_INIT$ltdl_init_args' to
$configure_ac.
+fi
+if $seen_ltdl || $opt_ltdl; then
# Remind the user to call LT_CONFIG_LTDL_DIR:
test -n $ac_ltdldir ||
func_echo Remember to add \`LT_CONFIG_LTDL_DIR([$ltdldir])' to
\`$configure_ac'.
@@ -961,13 +965,13 @@
func_echo Consider using
\`AC_CONFIG_AUX_DIR([${ltdlprefix}config])' in $configure_ac.
$ac_config_macro_dir_advised || test ${ltdlprefix}m4 = $m4dir ||
func_echo Consider using \`AC_CONFIG_MACRO_DIR([${ltdlprefix}m4])'
in $configure_ac.
-else
- # Don't trace for this, we're just checking the user didn't invoke it
- # directly from configure.ac.
- $SED 's,dnl .*$,,; s,# .*$,,' $configure_ac | grep AC_PROG_RANLIB
/dev/null
-func_echo \`AC_PROG_RANLIB' is rendered obsolete by \`LT_INIT'
fi
+# Don't trace for this, we're just checking the user didn't invoke it
+# directly from configure.ac.
+$SED 's,dnl .*$,,; s,# .*$,,' $configure_ac | grep AC_PROG_RANLIB
/dev/null
+ func_echo \`AC_PROG_RANLIB' is rendered obsolete by \`LT_INIT'
+
# FIXME: Ensure ltmain.sh, libtool.m4 and ltdl.m4 are from the same
release
}
@@ -1136,7 +1140,7 @@
if test -n $m4dir; then
$opt_quiet || func_echo putting macros in AC_CONFIG_MACRO_DIR,
\`$m4dir'.
-if $seen_ltdl; then
+if $opt_ltdl || $seen_ltdl; then
func_serial_update argz.m4 $aclocaldir $m4dir argz.m4
else
func_verbose Not copying \`$m4dir/argz.m4', libltdl not used.
@@ -1145,7 +1149,7 @@
func_serial_update libtool.m4 $aclocaldir $m4dir \
LT_INIT 'A[CM]_PROG_LIBTOOL'
-if $seen_ltdl; then
+if $opt_ltdl || $seen_ltdl; then
func_serial_update ltdl.m4 $aclocaldir $m4dir 'LTDL_INIT'
else
func_verbose Not copying \`$m4dir/ltdl.m4', libltdl not used.
@@ -1175,7 +1179,7 @@
# Copy all the files from installed libltdl to this project, if the
# user specified `--ltdl'.
- if $opt_ltdl; then
+ if $seen_ltdl || $opt_ltdl; then
# Unless we share CONFIG_MACRO_DIR with our parent project,
# copy macros here.
Index: tests/libtoolize.at
===
RCS file: /sources/libtool/libtool/tests/libtoolize.at,v
retrieving revision 1.13
diff -u -u -r1.13 libtoolize.at
--- tests/libtoolize.at 1 Jul 2007 20:55:13 - 1.13
+++ tests/libtoolize.at 25 Jan 2008 04:43:17 -
@@ -292,19 +292,10 @@
## Make sure ltdl.m4 is copied. ##
## ##
-AT_SETUP([copy ltdl.m4 with shared macro directory])
-
-AT_DATA([configure.ac],
-[[AC_INIT([libtoolize-demo], ]AT_PACKAGE_VERSION[, ]AT_PACKAGE_BUGREPORT[)
-LT_CONFIG_LTDL_DIR([ltdl])
-AC_CONFIG_AUX_DIR([ltdl/config])
-AC_CONFIG_MACRO_DIR([ltdl/m4])
-LT_INIT
-LT_WITH_LTDL
-AC_OUTPUT
-]])
-
-AT_DATA(expout,
+# _LT_AT_LTDL_SETUP
+# -
+m4_pushdef([_LT_AT_LTDL_SETUP],
+[AT_DATA(expout,
[[libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `ltdl/m4'.
libtoolize: linking file `ltdl/m4/argz.m4'
libtoolize:
