The configure script will choose a Fortran 95 compiler before it settles for a Fortran 77 one. Some of the code requires a Fortran 77 compiler, which means that, if you have more than one Fortran compiler installed, you'll have to force the build system with a command like:
where the Solaris Fortran 77 compiler is called% ./configure FC=f77 F77=f77 FPPFLAGS='-P -fixed' [other arguments]
f77. You
can give the path to the compiler also, if the f77 you want isn't the
first one in your PATH. Since this sort of robustness is
the sort of thing we'll continue to work on, don't do this until you
have empirically determined that it won't work otherwise.This dependence on a Fortran 77 compiler is true at present, and
may be the case indefinitely; at least part of the problem is the
current repository version of libtool,
which appears not to understand f95 on Solaris, so this
problem might
go away with a libtool update. As libtool doesn't understand the
FC flag, the F77 variable has to be set to
match the FC one.
The Solaris C and C++ compilers should work fine: if you have more
than one compiler installed, you can force the choice with the
configure arguments CC=cc and CXX=CC, but
this shouldn't be necessary. The system works with gcc and g++ on
Solaris, too, and these compilers can be selected using the same
mechanism.