LT 2.2.6 problem with Absoft compiler on Suse 9.3

[Jeff Squyres]

Greetings.  I previously posted about a problem with LT 2.2.4 and the
Absoft fortran compiler (http://lists.gnu.org/archive/html/bug-libtool/2008-05/msg00046.html 
); we finally had some more time to followup and get some more
information.  We upgraded to LT 2.2.6a, but as expected, the problem
still exists there as well (since we didn't provide any further info
for fixes to go into 2.2.6).

Attached is a trivial Automake project to build a simple F90 library.
Tony built this package on a few different platforms:

SUCCESS ON 32 bit CentOS 4.6 and GCC 3.4.6

make
/bin/sh ./libtool   --mode=compile f90   -c -o foo.lo foo.f90
libtool: compile:  f90 -c foo.f90  -fPIC -o .libs/foo.o
/bin/sh ./libtool   --mode=compile f90   -c -o bar.lo bar.f90
libtool: compile:  f90 -c bar.f90  -fPIC -o .libs/bar.o
/bin/sh ./libtool   --mode=link f90     -o libsample_f90.la -rpath /
usr/local/lib foo.lo bar.lo
libtool: link: f90 -shared  .libs/foo.o .libs/bar.o      -Wl,-soname -
Wl,libsample_f90.so.0 -o .libs/libsample_f90.so.0.0.0
libtool: link: (cd ".libs" && rm -f "libsample_f90.so.0" && ln -s
"libsample_f90.so.0.0.0" "libsample_f90.so.0")
libtool: link: (cd ".libs" && rm -f "libsample_f90.so" && ln -s
"libsample_f90.so.0.0.0" "libsample_f90.so")
libtool: link: ( cd ".libs" && rm -f "libsample_f90.la" && ln -s "../
libsample_f90.la" "libsample_f90.la" )


SUCCESS ON 64 bit SuSE 10.3 and GCC 4.2.1

make
/bin/sh ./libtool   --mode=compile f90   -c -o foo.lo foo.f90
libtool: compile:  f90 -c foo.f90  -fPIC -o .libs/foo.o
/bin/sh ./libtool   --mode=compile f90   -c -o bar.lo bar.f90
libtool: compile:  f90 -c bar.f90  -fPIC -o .libs/bar.o
/bin/sh ./libtool   --mode=link f90     -o libsample_f90.la -rpath /
usr/local/lib foo.lo bar.lo
libtool: link: f90 -shared  .libs/foo.o .libs/bar.o      -Wl,-soname -
Wl,libsample_f90.so.0 -o .libs/libsample_f90.so.0.0.0
libtool: link: (cd ".libs" && rm -f "libsample_f90.so.0" && ln -s
"libsample_f90.so.0.0.0" "libsample_f90.so.0")
libtool: link: (cd ".libs" && rm -f "libsample_f90.so" && ln -s
"libsample_f90.so.0.0.0" "libsample_f90.so")
libtool: link: ( cd ".libs" && rm -f "libsample_f90.la" && ln -s "../
libsample_f90.la" "libsample_f90.la" )



FAIL ON 32 bit SuSE 9.3 and GCC 3.3.5:

$ make
/bin/sh ./libtool   --mode=compile f90   -c -o foo.lo foo.f90
libtool: compile:  f90 -c foo.f90  -o .libs/foo.o
/bin/sh ./libtool   --mode=compile f90   -c -o bar.lo bar.f90
libtool: compile:  f90 -c bar.f90  -o .libs/bar.o
/bin/sh ./libtool   --mode=link f90     -o libsample_f90.la -rpath /
usr/local/lib foo.lo bar.lo
libtool: link: f90 -shared  .libs/foo.o .libs/bar.o       -soname
libsample_f90.so.0 -o .libs/libsample_f90.so.0.0.0
ERROR: Unrecognized arguments: -soname
ERROR: File not found: libsample_f90.so.0
make: *** [libsample_f90.la] Error 1


FAIL ON 64 bit SuSE 9.3 and GCC 3.3.3:

$ make
/bin/sh ./libtool   --mode=compile f90   -c -o foo.lo foo.f90
libtool: compile:  f90 -c foo.f90  -o .libs/foo.o
/bin/sh ./libtool   --mode=compile f90   -c -o bar.lo bar.f90
libtool: compile:  f90 -c bar.f90  -o .libs/bar.o
/bin/sh ./libtool   --mode=link f90     -o libsample_f90.la -rpath /
usr/local/lib foo.lo bar.lo
libtool: link: f90 -shared  .libs/foo.o .libs/bar.o       -soname
libsample_f90.so.0 -o .libs/libsample_f90.so.0.0.0
ERROR: Unrecognized arguments: -soname
ERROR: File not found: libsample_f90.so.0

The problem seems to be that LT is not inserting -Wl appropriately on
Suse 9.3.

Tony has also provided the stdout, stderr, and config.log from
building on Suse 10.3 (which succeeded) and Suse 9.3 (which failed),
and also a diff between the generated libtool scripts on these 2
platforms (see attached tarball).

One thing that jumps out at me is the following from the libtool diff:

8922c8921
< with_gcc=no
---
> with_gcc=yes

Could that be significant?  (I did not examine the configure stdout/
config.log's closely)

Any advice you have would be appreciated.  Thanks!

--
Jeff Squyres
Cisco Systems