CVS libtool prints an error message which implies that CC is not set when configuring for Fortran if no Fortran compiler is found. Libtool's Fortran support should be more graceful than this. Ideally it would short-circuit the Fortran configuration if no Fortran compiler is found. At a minimum, it shouldn't cause error messages to be printed.
checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for fl32... no checking for af77... no checking for fort77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for epcf90... no checking for f95... no checking for fort... no checking for xlf95... no checking for lf95... no checking for g95... no checking whether we are using the GNU Fortran 77 compiler... no . . . appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for option to produce PIC... -fPIC checking if PIC flag -fPIC works... no checking if supports -c -o file.o... no checking whether the linker (/usr/ccs/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... no checking dynamic linker characteristics... ./configure: -print-search-dirs: command not found solaris2.9 ld.so Can a maintainer of libtool's Fortran support attend to this or submit a patch? Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
