On the CRAY cluster where I am
While it’s possible that you have the MPICH that ships with the PGI compilers installed, I doubt it. If you did have it, it would be located in the “$PGI/linux86-64/2011/mpi” directory.
If is not installed, then you will need to remove the “-Mmpi=mpich” flag and change your compilers to “mpicc” and “mpif90”. You will also need to make sure the xt-mpich2 module uses a PGI built MPICH2 package. To check run “mpif90 -V”. (-V is PGI’s version flag).
the problem is that it “leaved” and it didn’t compile the mpi folder.
Can you find out why? Do you have a log of the build? I’m guessing that it’s due to the lack of MPI header files, but don’t know for sure.
FYI, it doesn’t appear that the “–enable-mpi” has any sub options. I think configure would just ignore the “=/opt/cray/xt-asyncpe/4.7/bin/cc” but it’s possible that it’s ignoring the entire flag. Try using just the “–enable-mpi” option.
/usr/bin/ld: attempted static link of dynamic object `…/.libs/libfftw3.so’
Since this is a CRAY system, I’m assuming your using the Catamount OS. If I remember right, Catamount does support shared libraries and you need to remove the “–enable-shared” option.
After the make install the serial code compiled Ok but the mpi not. The main problem is that it could not “make” in the fftw3.3alpha/mpi folder.
You’ll need to do more digging as to exactly why if my above suggestions don’t work.