[cmake-developers] [CMake 0014347]: FindMPI sets MPIEXEC to wrong executable
Mantis Bug Tracker
mantis at public.kitware.com
Fri Aug 9 10:37:09 EDT 2013
The following issue has been SUBMITTED.
======================================================================
http://public.kitware.com/Bug/view.php?id=14347
======================================================================
Reported By: Marcel Loose
Assigned To:
======================================================================
Project: CMake
Issue ID: 14347
Category: Modules
Reproducibility: always
Severity: minor
Priority: normal
Status: new
======================================================================
Date Submitted: 2013-08-09 10:37 EDT
Last Modified: 2013-08-09 10:37 EDT
======================================================================
Summary: FindMPI sets MPIEXEC to wrong executable
Description:
When MPI is installed in a non-standard location (which is the rule, rather than
the exception on cluster systems), FindMPI will not find the correct mpiexec.
Though you can help FindMPI to find the correct compilers, by setting
MPI_<lang>_COMPILER variables, there's no way to do this for MPIEXEC.
Steps to Reproduce:
1. Have MPI installed in a non-standard directory, e.g., /opt/openmpi
2. Create a CMakeLists.txt file that contains a line "find_package(MPI)
3. Check the cache for the value of the different MPI variables
Additional Information:
I think that the CMake|environment variable MPI_HOME should be used as HINTS in
the call of find_program for mpiexec. Subsequently, _MPI_BASE_DIR (as derived
from the path to mpiexec) can be used as HINTS in the call of find_program of
the MPI compiler(s).
I've attached a patch that solves this problem.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2013-08-09 10:37 Marcel Loose New Issue
2013-08-09 10:37 Marcel Loose File Added: FindMPI.patch
======================================================================
More information about the cmake-developers
mailing list