From e6d3ab84059cf878a1621fd450b062c46cae785c Mon Sep 17 00:00:00 2001 From: Cameron Smith Date: Fri, 13 Apr 2018 14:53:26 -0400 Subject: cray: add comment about module use in packages.yaml (#7751) This advises users to prefer `modules:` entries in `packages.yaml` on Cray. --- lib/spack/docs/getting_started.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'lib') diff --git a/lib/spack/docs/getting_started.rst b/lib/spack/docs/getting_started.rst index 48999ad152..407c1774b8 100644 --- a/lib/spack/docs/getting_started.rst +++ b/lib/spack/docs/getting_started.rst @@ -1203,7 +1203,14 @@ Here's an example of an external configuration for cray modules: This tells Spack that for whatever package that depends on mpi, load the cray-mpich module into the environment. You can then be able to use whatever environment variables, libraries, etc, that are brought into the environment -via module load. +via module load. + +.. note:: + + For Cray-provided packages, it is best to use ``modules:`` instead of ``paths:`` + in ``packages.yaml``, because the Cray Programming Environment heavily relies on + modules (e.g., loading the ``cray-mpich`` module adds MPI libraries to the + compiler wrapper link line). You can set the default compiler that Spack can use for each compiler type. If you want to use the Cray defaults, then set them under ``all:`` in packages.yaml. -- cgit v1.2.3-70-g09d2