I forgot to mention: Brian and I chatted today and we have both been
building the 1.2 branch with AM 1.10 / AC 2.61 for a long time and
it's been fine.
So we're throwing it on the to-do list to upgrade the nightly tarball
generation process to AM 1.10 / AC 2.61.
As for upgrading the Libtool 2.1 that we use -- maybe we'll wait for
the upcoming xlc fixes (if there's no urgent need to upgrade and the
xlc stuff might be in within the next few weeks). :-)
On Aug 6, 2007, at 2:48 PM, Ralf Wildenhues wrote:
Hello Jeff,
* Jeff Squyres wrote on Mon, Aug 06, 2007 at 04:27:59PM CEST:
On Aug 5, 2007, at 3:41 PM, Ralf Wildenhues wrote:
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).
[...]
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.
[...]
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):
Ahh, yes, that was the patch that fixed the problem (rather than the
Autoconf upgrade), I remember now. Thanks for searching!
--- 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'
else
GXX=no
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... :-)
The patch has two issues. First a simple one, it should be
sed -n '$p'
instead of `tail -n 1', for portability. Second, and more
importantly,
I remember to have tested the patch on some but not all compilers
that I
know do pretend to be g++ at times (icpc, pathCC?, pgCC?). I hope
none
of them (nor g++ either) get the idea of splitting long output
lines of
`$CXX -v' with backslash-newline.
Anyway, I'll put on my list throwing out another test round for the
patch.
Cheers,
Ralf
_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
--
Jeff Squyres
Cisco Systems
