Peter O'Gorman wrote: > Nelson H. F. Beebe wrote: > > >>> libtool: link: f90 -shared -Qoption ld --whole-archive ./.libs/liba1.a >>> ./.libs/liba2.a -Qoption ld --no-whole-archive -Qoption ld -soname >>> -Qoption ld liba12.so.0 -o .libs/liba12.so.0.0.0 >>> /convenience.at:211: exit code was 1, expected 0 >>> 18. convenience.at:169: 18. FC convenience archives (convenience.at:169): >>> FAILED (convenience.at:211) > > Libtool detected FC as f90, but otherwise used the gcc tools. I'll look > into this. >
Because we generally use the same archive_cmds for F77, FC as for CXX, things can get a little messed up. This "fixes" the most common case, gcc, g++, g77/gfortran & some other fortran compiler, by pretending the "other fortran compiler" does not exist. Thoughts? Peter -- Peter O'Gorman http://pogma.com
2008-03-06 Peter O'Gorman <[EMAIL PROTECTED]> * libltdl/m4/libtool.m4 (_LT_PROG_FC): Report FC=no if the FC compiler is not a GNU compiler and the CXX compiler is a GNU compiler. Reported by Nelson H. F. Beebe. Index: libltdl/m4/libtool.m4 =================================================================== RCS file: /sources/libtool/libtool/libltdl/m4/libtool.m4,v retrieving revision 1.138 diff -u -r1.138 libtool.m4 --- libltdl/m4/libtool.m4 4 Mar 2008 21:14:22 -0000 1.138 +++ libltdl/m4/libtool.m4 7 Mar 2008 01:00:35 -0000 @@ -6644,6 +6644,15 @@ if test -z "$FC" || test "X$FC" = "Xno"; then _lt_disable_FC=yes fi + +# If g++ is being used, but the fortran compiler is not a gnu +# compiler, we should simply ignore it. It will not grok -shared, for +# example. +if test "x$ac_cv_fc_compiler_gnu" != "x$GXX"; then + FC=no + _lt_disable_FC=yes +fi + popdef([AC_MSG_ERROR]) ])# _LT_PROG_FC
_______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool