Chris,

.mod files are compiler-specific, and may even be version-specific.  You may, 
however, be lucky enough to compile the Fortran interface definitions with 
ifort and supply that mpi.mod to ifort, even though the actual code was 
compiled with gfortran.  I have never tried that -- we build separate 
development trees for each OpenMPI version/compiler product/compiler version.

Larry Baker
US Geological Survey
650-329-5608
ba...@usgs.gov



On 22 Aug 2013, at 6:50 AM, Jeff Squyres (jsquyres) wrote:

> Sadly, probably not. :(. You'll prbably have the same problem with c++, too. 
> 
> There *may* be compatibility command line options for ifort/icpc to make them 
> link compatible w gfortran/g++, but I've never had much faith in them. 
> 
> Sent from my phone. No type good. 
> 
> On Aug 22, 2013, at 2:24 AM, "Christopher Samuel" <sam...@unimelb.edu.au> 
> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> Hi folks,
>> 
>> We've got what we thought would be a fairly standard OMPI (1.6.5)
>> install which is a single install built with GCC and then setting the
>> appropriate variables to use the Intel compilers when someone loads
>> our "intel" module:
>> 
>> $ module show intel
>> [...]
>> setenv           OMPI_CC icc
>> setenv           OMPI_CXX icpc
>> setenv           OMPI_F77 ifort
>> setenv           OMPI_FC ifort
>> setenv           OMPI_CFLAGS -xHOST -O3 -mkl=sequential
>> setenv           OMPI_FFLAGS -xHOST -O3 -mkl=sequential
>> setenv           OMPI_FCFLAGS -xHOST -O3 -mkl=sequential
>> setenv           OMPI_CXXFLAGS -xHOST -O3 -mkl=sequential
>> 
>> This works wonderfully, *except* when our director attempted to build
>> an F90 program with the Intel compilers that fails to build because
>> the mpi.mod F90 module was produced with gfortran rather than the
>> Intel compilers. :-(
>> 
>> Is there any way to avoid having to do parallel installs of OMPI with
>> GCC and Intel compilers just to have two different versions of these
>> files?
>> 
>> My brief googling hasn't indicated anything, and I don't see anything
>> in the mpif90 manual page (though I have to admit I've had to rush to
>> try and get this done before I need to leave for the day). :-(
>> 
>> cheers,
>> Chris
>> - -- 
>> Christopher Samuel        Senior Systems Administrator
>> VLSCI - Victorian Life Sciences Computation Initiative
>> Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545
>> http://www.vlsci.org.au/      http://twitter.com/vlsci
>> 
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>> 
>> iEYEARECAAYFAlIVrpIACgkQO2KABBYQAh/GAQCggQGnc18kSfMcGle3a3pWZGgD
>> UQ8AoIz61uuOPj+TFJwSYMTaAtUBLk3J
>> =yJ6J
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org
>> http://www.open-mpi.org/mailman/listinfo.cgi/devel
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel

Reply via email to