[MPICH] Cannot determine Fortran naming scheme?

Anthony Chan chan at mcs.anl.gov
Thu Apr 20 13:14:44 CDT 2006

On Thu, 20 Apr 2006, David Gunter wrote:

> MPICH2 requires
>         setenv CC pgcc
> (or export CC=pgcc for ksh or CC=pgcc ; export CC for strict sh) before
> ./configure. Basically, every option to the MPICH-1 configure that does
> not start with --enable or --with is not available as a configure
> option in
> MPICH2. Instead, environment variables must be used. This is consistent
> (and required) for use of version 2 GNU autoconf. "

later versions of MPICH2 uses autoconf 2.5x which allows environmental
variables to be passed on the command line. In fact, it is the recommended
way of passing env. variables as suggested here:


> On Apr 20, 2006, at 12:31 AM, Grus Weir wrote:
> > Hi all,
> >     I'm just a newbie.
> >     When I am trying to install mpich2-1.0.3 on my linux machine.
> >     My system is SUSE 9.3/gcc-3.3.5-5/pgi6.0-5
> > after
> >    ./configure --prefix=/software/mpich2 --enable-f77 --enable-f90
> > --enable-cxx LDFLAGS='-lm' CC=gcc CXX=g++ CPP='g++ -E' F77=pgf90
> > F90=pgf90 > configure.log 2>configure.error

Your configure command was running fine on a debian3.1 box with
gcc-3.3.5 + pgi5.2(the latest that I have access to) and I was able
to use mpif77/mpif90 to compile/link simple fortran program.  (A
simple way to check if the compiler wrappers work is to do a
"make installcheck" after "make install".)  Though I did see the same
pgf90 warnings (some of the warnings are from libtool used by slog2sdk).
If your mpich2 installation still does not work, try

<mpich2-103>/configure --prefix=/software/mpich2 \
  CC=gcc CXX=g++ F77=pgf77 F90=pgf90 --disable-rlog --disable-sample \
 | tee c.txt 2>&1

Send/Post your c.txt if problem remain. (Don't pipe your stdout and
stderr into 2 separate files! We can't tell what cause those warnings)


More information about the mpich-discuss mailing list