[cmake-developers] [CMake 0014872]: FindMPI.cmake finds MPI of different compiler
Mantis Bug Tracker
mantis at public.kitware.com
Thu Apr 10 15:23:58 EDT 2014
The following issue has been SUBMITTED.
======================================================================
http://www.cmake.org/Bug/view.php?id=14872
======================================================================
Reported By: Melven Roehrig-Zoellner
Assigned To:
======================================================================
Project: CMake
Issue ID: 14872
Category: CMake
Reproducibility: always
Severity: tweak
Priority: low
Status: new
======================================================================
Date Submitted: 2014-04-10 21:23 CEST
Last Modified: 2014-04-10 21:23 CEST
======================================================================
Summary: FindMPI.cmake finds MPI of different compiler
Description:
On the machine I'm using here there are multiple compilers and MPI variants in
the PATH:
More precisely ifort, gfortran and pgf90 in the PATH and each of them brings
their own MPI wrappers (one could argue that this is already a bug of the
system, but I'm not the admin...).
So without setting any additional environment-variables, cmake detects ifort as
Fortran compiler and the MPI-wrapper mpif90 from PGI. As a result one obtains
possibly strange compiler errors during make.
It would be helpful to get at least an error from cmake if the compiler ID (or
version) of MPI_Fortran_COMPILER and CMAKE_Fortran_COMPILER differ...
Most probably the same effects could also occur for C / C ++, but I have not
tested other languages than Fortran.
Steps to Reproduce:
Install compilers from different vendors and a specific MPI variant for each
them. Then put all compilers and at least one MPI variant in the path.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2014-04-10 21:23 Melven Roehrig-ZoellnerNew Issue
======================================================================
More information about the cmake-developers
mailing list