On Fri, 21 Nov 2003, Gary V. Vaughan wrote: > I can't remove this because the dist will fail without it. This rule descends > into the testdirs and runs their configure scripts, in order that when the > dist rule proper calls upon the testdir Makefile's own dist rule, the Makefile > is already there. > > | Besides, it often doesn't work and it can take a very long time: > > This must be because you haven't executed the testsuite: Notice that the > configure is only run for each testsuite Makefiles (@DIST_MAKEFILE_LIST@) that > is out of date. > > | checking for Fortran 77 name-mangling scheme... configure: error: > | cannot compile a simple Fortran program > | See `config.log' for more details. > | make: *** [tests/f77demo/Makefile] Error 1 > > This is telling you that you haven't tested the f77 support in libtool before > you are rolling a distribution.
Even though the OS happens to be Linux, there is no Fortran install on this box. It would be smart for the Libtool tests to change language tests from "Fail" to "Untested" if the required compiler is not available. That way 'make check' can succeed based on the available compilers. This would seem to be a requirement for non-GCC environments. Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
