You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorial_stacks.rst
+7-28Lines changed: 7 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,11 +39,11 @@ Setup the compiler
39
39
The first step to build our stack is to setup the compiler we want to use later.
40
40
This is currently an iterative process that can be done in two ways:
41
41
42
-
1. Install the compiler first, then register it in the environment
43
-
2. Use a second environment just for the compiler
42
+
1. Install the compiler first, then install the rest of the environment
43
+
2. Install the compiler outside the environment (either in another environment or standalone)
44
44
45
45
Below, we'll use the first approach.
46
-
For people interested, an example of the latter approach can be found `at this link <https://github.com/haampie/spack-intermediate-gcc-example/>`_.
46
+
For people interested, an example of composing a compiler from another environment can be found `at this link <https://github.com/haampie/spack-intermediate-gcc-example/>`_.
47
47
48
48
Let's start by creating an environment in a directory of our choice:
49
49
@@ -67,27 +67,6 @@ The next step is to concretize and install our compiler:
67
67
.. literalinclude:: outputs/stacks/setup-2.out
68
68
:language: console
69
69
70
-
Finally, let's register it as a new compiler in the environment:
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``.
418
397
@@ -444,7 +423,7 @@ To address all these needs we can complicate our ``modules`` configuration a bit
0 commit comments