On Fri, 4 Dec 2009 16:20:23 -0500, Jeff Squyres <jsquy...@cisco.com> wrote: > Oy -- more specifically, we should not be putting -I/usr/include on > the command line *at all* (because it's special and already included > by the compiler search paths; similar for /usr/lib and /usr/lib64).
If I remember correctly, the issue was that some versions of gfortran were not searching /usr/include for mpif.h. > Can you send the contents of your > $prefix/share/openmpi/mpif90-wrapper-data.txt? Attached. Jed
# There can be multiple blocks of configuration data, chosen by # compiler flags (using the compiler_args key to chose which block # should be activated. This can be useful for multilib builds. See the # multilib page at: # https://svn.open-mpi.org/trac/ompi/wiki/compilerwrapper3264 # for more information. project=Open MPI project_short=OMPI version=1.3.4 language=Fortran 90 compiler_env=FC compiler_flags_env=FCFLAGS compiler=/usr/bin/gfortran module_option=-I extra_includes= preprocessor_flags= compiler_flags=-pthread linker_flags= libs=-lmpi_f90 -lmpi_f77 -lmpi -lopen-rte -lopen-pal -ldl -Wl,--export-dynamic -lnsl -lutil -lm -ldl required_file= includedir=${includedir} libdir=${libdir}
