summaryrefslogtreecommitdiff
path: root/.coveragerc
diff options
context:
space:
mode:
authorKelly (KT) Thompson <kgt@lanl.gov>2016-10-10 18:57:35 -0600
committerKelly (KT) Thompson <kgt@lanl.gov>2016-10-10 19:10:26 -0600
commit3553c8b9e92f81e53c607c574b1b746e03039ac7 (patch)
tree01c1ab9173583bbd4febd1623a57ff0baa85e19f /.coveragerc
parent29fc9cd22c4d4cf600ec5982f2f43c9941539e7f (diff)
downloadspack-3553c8b9e92f81e53c607c574b1b746e03039ac7.tar.gz
spack-3553c8b9e92f81e53c607c574b1b746e03039ac7.tar.bz2
spack-3553c8b9e92f81e53c607c574b1b746e03039ac7.tar.xz
spack-3553c8b9e92f81e53c607c574b1b746e03039ac7.zip
On Cray machines, use the Cray compile wrappers instead of MPI wrappers.
+ Cray compile wrappers are MPI wrappers. + Packages that need to be compiled with MPI compile wrappers normally use 'mpicc', 'mpic++' and 'mpif90' provided by the MPI vendor. However, when using cray-mpich as the MPI vendor, the compile wrappers 'CC', 'cc' and 'ftn' must be used. + In this scenario, the mpich package is hijacked by specifying cray-mpich as an external package under the 'mpich:' section of packages.yaml. For example: packages: mpich: modules: mpich@7.4.2%intel@16.0.3 arch=cray-CNL-haswell: cray-mpich/7.4.2 buildable: False all: providers: mpi: [mpich] + This change allows packages like parmetis to be built using the Cray compile wrappers. For example: 'spack install parmetis%intel@16.0.3 ^mpich@7.4.2 os=CNL' + This commit relies on the existence of the environment variable CRAYPE_VERSION to determine if the current machine is running a Cray environment. This check is insufficient, but I'm not sure how to improve this logic. + Fixes #1827
Diffstat (limited to '.coveragerc')
0 files changed, 0 insertions, 0 deletions