I've finally stumbled over it (Cc'ing the bug reporters and everybody
who's been helpful). Of course I'd been looking in the completely wrong
place before..
For the benefit of readers that did not follow closely: There was also
a libtool bug, which has been fixed soon after Pierre reported the lam
build failure with 64bit Solaris.
But..
> * fjcsuper_at_[hidden] wrote on Tue, Jan 18, 2005 at 04:28:45AM CET:
> > Ralf Wildenhues wrote on Mon, 17 Jan 2005 11:43:10 +0100
> >
> > >Most likely, the problem occurs earlier. During compile, >libtool munges
> > >the -xarch=amd64. Can you confirm this by looking at what >libtool calls
> > >when the sources to liblam.la are compiled?
..this failure is a LAM bug. Minimal, untested patch below.
I should note that the way of getting at flags by grepping Makefiles is
quite brittle and could be subject to all sorts of interesting failures.
E.g., configure could output
LIBS = -la \
-lb
or make use of other variables or whatever. None of this is specified
by Automake. (One could replace `egrep | cut' with a little sed hackery
to prepare for the first issue.)
Furthermore, there are a couple more such places where I'm not sure a
similar thing could happen. However, I don't know LAM well enough to be
able to decide.
Thanks for your patience and help.
Regards,
Ralf
* configure.in: Fix extraction of link flags.
diff -u orig/configure.in trillium/configure.in
--- orig/configure.in 2005-01-19 17:36:30.589600680 +0100
+++ trillium/configure.in 2005-01-19 17:39:05.836999488 +0100
@@ -1976,8 +1976,8 @@
dir="$LAM_TOP_BUILDDIR/share/ssi/$kind/$m"
lt="$dir/libtool"
if test -x "$lt" -a -f "$dir/Makefile"; then
- flags1="`egrep '^LDFLAGS[ \t]*=' $dir/Makefile | cut -d= -f2`"
- flags2="`egrep '^LIBS[ \t]*=' $dir/Makefile | cut -d= -f2`"
+ flags1="`egrep '^LDFLAGS[ \t]*=' $dir/Makefile | cut -d= -f2-`"
+ flags2="`egrep '^LIBS[ \t]*=' $dir/Makefile | cut -d= -f2-`"
LAM_CHECK_LINKER_FLAGS([$lt], [$flags1 $flags2])
for flag in $extra_ldflags; do
|
