Martin wrote:
>configure.in:20: warning: AC_PROG_CPP was called before AC_PROG_F77
>configure.in:21: warning: AC_PROG_F77 was called before AC_PROG_F77_C_O
These seem bogus to me, too.
>Another issue: I question whether "g77" should really be the first-choice
>Fortran compiler on systems with both GNU and native compilers
>installed. Although I do prefer free software to commercial software, I
>picture that people who paid $1000 or more for a commercial fortran
>compiler may want to use that one (especially since g77 has some
>significant drawbacks), without having to type "F77=f77 ./configure" all
>the time.
One practical problem with not putting g77 first is inconsistency with the
C compiler. That is, gcc is the first-choice C compiler and this is
unlikely to change, and in my experience mixing gcc with vendor Fortran
compilers can cause all sorts of problems (e.g. on machines like SGI with
multiple binary formats, gcc and f77 might have different defaults). It is
not something I would recommend doing by default.
(Individual packages for which performance is extremely important, and for
which g77 and/or gcc are unsatisfactory, can easily force both cc and f77
to be the defaults by calling AC_CHECK_PROGS before AC_PROG_CC/F77.)
If the user really wants to use f77 all of the time, they can always set
the F77 environment variable in their dotfiles or put it in config.site.
Or delete g77, for that matter.
Cordially,
Steven G. Johnson
