On Aug 5, 2007, at 3:41 PM, Ralf Wildenhues wrote:
>> WHAT: Upgrade to a newer Libtool 2.1 nightly snapshot (we are
>> currently using 1.2362 2007/01/23) for making OMPI tarballs.
>> WHY: https://svn.open-mpi.org/trac/ompi/ticket/982 is fixed by newer
>> Libtool snapshots (e.g., 1.2444 2007/04/10 is what I have installed
>> at Cisco).
> Is it? If so, then I would like to know why (config.log outputs for
> both would be nice). Could have been an Autoconf update instead.
> Asking because I don't think the bug was consciously fixed in Libtool;
> only a test was added to expose the issue. I'll put it on my list of
> things to look at.
While gathering data for this reply, I realized that you are exactly
right: it's not the difference in the versions of Libtool that is the
problem, it's the difference in versions of Autoconf (the OMPI v1.2
nightly tarball uses AC 2.59, the OMPI trunk nightly tarball uses AC
2.61, I use AC 2.61 in my development copies).
So I'll change my RFC and send it around again to upgrade the version
of AC that we're using in the 1.2 tarball. There may be some second-
order effects of doing this; I'll chat with Brian about it (he
watches this stuff much more closely than me).
FWIW, note that we are applying this patch to the generated
aclocal.m4 (in all versions -- it appears to apply cleanly with a
little fuzz on the exact line numbering):
--- aclocal.m4.old 2007-04-20 15:18:48.000000000 -0700
+++ aclocal.m4 2007-04-20 15:18:59.000000000 -0700
@@ -5311,7 +5311,7 @@
# Commands to make compiler produce verbose output that lists
# what "hidden" libraries, object files and flags are used when
# linking a shared library.
- output_verbose_link_cmd='$CC -shared $CFLAGS -v conftest.
$objext 2>&1 | $GREP "\-L"'
+ output_verbose_link_cmd='$CC -shared $CFLAGS -v conftest.
$objext 2>&1 | $GREP "\-L" | tail -n 1'
This fixes the problem for us (we stole it from a libtool mailing
list post from a long time ago). If this could be applied to the
Libtool development trunk, that would be great... :-)
>> Plus, it's a newer version, so it's better, right? ;-)
> FWIW, a patch applied today fixes a regression introduced on
> and reported by Brian.
> devel mailing list