Can you double check that you are using the wrapper compilers from the
Open MPI installation that you think you're using?
Tiger doesn't ship with Open MPI, so you shouldn't have problems
conflicting with a system-installed OMPI, but could you possibly have
another OMPI install hanging around somewhere?
What is the output of mpicc --showme, mpicxx --showme, mpif77 -showme,
and mpif90 --showme?
If the intel compilers are not defaulting to 64 bit, you might also
need to add -m64 to your wrapper compiler command line, e.g.:
shell$ mpif90 hello_f90.f90 -m64
You can add flags to the wrapper compilers with the following:
--with-wrapper-cflags Extra flags to add to CFLAGS when using mpicc
--with-wrapper-cxxflags Extra flags to add to CXXFLAGS when using
--with-wrapper-fflags Extra flags to add to FFLAGS when using
--with-wrapper-fcflags Extra flags to add to FCFLAGS when using
--with-wrapper-ldflags Extra flags to add to LDFLAGS when using
--with-wrapper-libs Extra flags to add to LIBS when using wrapper
Or you can edit the text files in $prefix/share/openmpi/*-wrapper-
On Apr 17, 2008, at 12:55 AM, Rodriguez, Jose wrote:
> Dear OMPI users and builders:
> I recently installed the latest version of Open MPI (1.2.6) on my
> Mac Pro, which has 2 dual-core Intel cpu's.
> On the plus side, I can successfully compile and run MPI codes
> written both in fortran77 and in c on all 4 cores
> with the corresponding wrappers that the build created. On the down
> side, I cant compile the fortran90
> and the c++ versions of the sample `hello world' MPI programs.
> Instead I get
> ".../mpi_examples jpr$ mpif90 hello_f90.f90
> fortcom: Error: hello_f90.f90, line 12: This module file was not
> generated by any release of this compiler. [MPI]
> use mpi --------^
> fortcom: Error: hello_f90.f90, line 17: This name does not have a
> and must have an explicit type. [MPI_COMM_WORLD]
> call MPI_COMM_RANK(MPI_COMM_WORLD, rank, ierr)
> compilation aborted for hello_f90.f90 (code 1)"
> ".../mpi_examples jpr$ mpicxx hello_cxx.cc
> ld64 warning: in /usr/local/lib/libstdc++.dylib, file is not of
> required architecture
> ld64-62.1 failed: can't open file for writing".
> Does anyone know what's wrong here? I configured the build using all
> of the latest Intel compilers:
> $ ./configure CC=icc CXX=icpc F77=ifort FC=ifort CFLAGS=-m64
> CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 --with-mpi-f90-size=medium.
> Last, I'm running Mac OS Tiger (10.4.11) and Xcode 2.4.1. And
> apropos my version of GCC, I have
> "diana:~ jpr$ GCC
> i686-apple-darwin8-gcc-4.0.1: no input files".
> Any guidance would be greatly appreciated.
> Jose Rodriguez, Physics and Astronomy, California State University
> at Los Angeles, April 16, 2008.
> users mailing list