cray: add comment about module use in packages.yaml (#7751)
This advises users to prefer `modules:` entries in `packages.yaml` on Cray.
This commit is contained in:
parent
b9c8cdcbe3
commit
e6d3ab8405
@ -1205,6 +1205,13 @@ 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.
|
||||||
In the compiler field, set the compiler specs in your order of preference.
|
In the compiler field, set the compiler specs in your order of preference.
|
||||||
|
Loading…
Reference in New Issue
Block a user