Nelson H. F. Beebe wrote: > libtool: link: (cd .libs/liba12.lax/liba1.a && ar x > "/local/build/bare/libtool-2.2/tests/testsuite.dir/18/./.libs/liba1.a") > libtool: link: (cd .libs/liba12.lax/liba2.a && ar x > "/local/build/bare/libtool-2.2/tests/testsuite.dir/18/./.libs/liba2.a") > libtool: link: f95 -shared -expect_unresolved \* > .libs/liba12.lax/liba1.a/a1.o .libs/liba12.lax/liba2.a/a2.o -msym > -soname liba12.so.0 `test -n "0.0.0:0.0" && /usr/local/bin/echo > "X-set_version 0.0.0:0.0" | /usr/local/bin/sed -e 1s/^X//` -update_registry > .libs/so_locations -o .libs/liba12.so.0.0.0 > f95: Severe: Invalid file name - must be of the form name.suffix : *
Ok, it really should not be using the results of the F77 checks to generate shared libraries for FC. We saw this with your solaris results too. > stderr: > stdout: > ./shlibpath.at:66: exit code was 1, expected 0 > 23. shlibpath.at:25: 23. shlibpath_overrides_runpath (shlibpath.at:25): > FAILED (shlibpath.at:66) > Hmm. We have access to an OSF1/Alpha system, so will look into this. > stdout: > ./nonrecursive.at:114: CONFIG_SHELL=$SHELL $SHELL ./configure > $configure_options > stderr: > ./config.status[672]: syntax error at line 775 : `newline or ;' unexpected That's strange! > stdout: > checking for a BSD-compatible install... /usr/local/bin/install -c > configure: error: C compiler cannot create executables > See `config.log' for more details. > And so is this. Thanks, Peter _______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool
