Skip to content

Commit 0825495

Browse files
committed
fix bug with core_compilers not working properly
Signed-off-by: Gregory Becker <becker33@llnl.gov>
1 parent 657cf64 commit 0825495

3 files changed

Lines changed: 5 additions & 0 deletions

File tree

outputs/stacks/examples/8.spack.stack.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,3 +38,5 @@ spack:
3838
hierarchy:
3939
- mpi
4040
- lapack
41+
core_specs:
42+
- '%gcc@11'

outputs/stacks/examples/9.spack.stack.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,8 @@ spack:
3838
hierarchy:
3939
- mpi
4040
- lapack
41+
core_specs:
42+
- '%gcc@11'
4143
hash_length: 0
4244
include:
4345
- gcc

tutorial_stacks.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -396,6 +396,7 @@ The next step is to add some basic configuration to our ``spack.yaml`` to genera
396396
:emphasize-lines: 31-40
397397

398398
In these few lines of additional configuration we told Spack to generate ``lmod`` module files in a subdirectory named ``modules``, using a hierarchy comprising both ``lapack`` and ``mpi``.
399+
We've also configured it to place all specs built with our system compiler into the ``Core`` designation in the lmod hierarchy.
399400

400401
We can generate the module files and use them with the following commands:
401402

0 commit comments

Comments
 (0)