zhangyiss/spack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cray: add comment about module use in packages.yaml (#7751)

Browse Source 
This advises users to prefer `modules:` entries in `packages.yaml` on Cray.
This commit is contained in:
Cameron Smith 2018-04-13 14:53:26 -04:00 committed by Todd Gamblin
parent b9c8cdcbe3
commit e6d3ab8405
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
lib/spack/docs/getting_started.rst
View File

@ -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 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 cray-mpich module into the environment. You can then be able to use whatever
environment variables, libraries, etc, that are brought into the environment 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. 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. If you want to use the Cray defaults, then set them under ``all:`` in packages.yaml.