Hello --
I'm attempting to test the functionality of the gfortran compiler
that is included in the gcc 4.0.3 source release on an Intel-based
Mac with OS X 10.4. I have built gcc from scratch and built my LAM-
MPI configuration to have the C compiler to be gcc and the FORTRAN
compiler be gfortran. I'm hoping that the original build of the
compilers was successful, and was hoping to use LAM-MPI as my first
bit test (I have tried building small simple files with gfortran and
it compiled them successfully).
LAM-MPI appears to build successfully, and the next logical step is
for me to extract, configure, make, and run the test suite from your
site. However, here is an error I get when I run the configure from
the test suite:
perfeval15:~/Projects/lamtests-7.1.2 peg$ ./configure
Configuring LAM test suite version 7.1.2
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking build system type... i386-apple-darwin8.6.2
checking host system type... i386-apple-darwin8.6.2
checking for mpicc... yes
checking for gcc... mpicc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether mpicc accepts -g... yes
checking for mpicc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of mpicc... gcc3
checking for mpic++... yes
checking whether we are using the GNU C++ compiler... yes
checking whether mpic++ accepts -g... yes
checking dependency style of mpic++... gcc3
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... 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 ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
checking for ranlib... ranlib
checking for mpi.h... yes
checking for MPI_Initialized in -lmpi... yes
checking if have Fortran MPI bindings... no
checking if supposed to have Fortran MPI bindings... yes
configure: error: Cannot continue
Now, it is a problem that gfortran is being seen as the GNU Fortran
77 compiler, right? It is supposed to be an F90 or F95 equivalent
compiler, correct? Could this be the cause of the errors where it
dies at the MPI bindings? Are there any build options I can do when I
initially build LAM-MPI or for the lamtests that will work around
this problem?
Thanks!
Bryan
|
