spack backports branch + toolchain updates (#273)

outputs/defs.sh

@@ -14,7 +14,7 @@ fi
 raw_outputs="${PROJECT}/raw"
 
 # used by scripts
-tutorial_branch=releases/v0.21
+tutorial_branch=backports/v0.21.0
 
 print_status() {
     printf "\n%b: %s\n\n" "\033[1;35m$1\033[0m" "$2"

outputs/modules.sh

@@ -22,10 +22,10 @@ spack install lmod
 
 . "$(spack location -i lmod)/lmod/lmod/init/bash"
 . share/spack/setup-env.sh
-spack install gcc@12.1.0
+spack install gcc@12
 
-example --tee modules/spack-load-gcc "spack load gcc@12.1.0"
-spack load gcc@12.1.0
+example --tee modules/spack-load-gcc "spack load gcc@12"
+spack load gcc@12
 example      modules/spack-load-gcc "which gcc"
 
 example      modules/add-compiler   "spack compiler add"
@@ -44,7 +44,7 @@ spack install py-scipy ^openblas
 example --tee modules/module-avail-2 "module avail"
 
 gcc_hash="$(spack find --format '{hash:7}' gcc)"
-gcc_module="gcc-12.1.0-gcc-11.3.0-${gcc_hash}"
+gcc_module="gcc/12.3.0-gcc-11.4.0-${gcc_hash}"
 example --tee modules/module-show-1  "module show $gcc_module"
 
 spack config add "modules:default:tcl:all:filter:exclude_env_vars:['C_INCLUDE_PATH', 'CPLUS_INCLUDE_PATH', 'LIBRARY_PATH']"
@@ -53,7 +53,7 @@ example  modules/tcl-refresh-1          "spack module tcl refresh -y"
 example --tee modules/module-show-2     "module show $gcc_module"
 
 
-spack config add                        "modules:default:tcl:exclude:['%gcc@11.3.0']"
+spack config add                        "modules:default:tcl:exclude:['%gcc@11']"
 example      modules/tcl-refresh-2      "spack module tcl refresh --delete-tree -y"
 example --tee modules/module-avail-3    "module avail"
 

outputs/scripting.sh

@@ -7,11 +7,11 @@ project="$(dirname "$0")"
 rm -rf "${raw_outputs:?}/scripting"
 . "$project/init_spack.sh"
 
-spack install gcc@12.1.0
-spack compiler find "$(spack location -i gcc@12.1.0)"
+spack install gcc@12
+spack compiler find "$(spack location -i gcc@12)"
 
 example scripting/setup           "spack uninstall -ay"
-example scripting/setup           "spack compiler rm gcc@12.1.0"
+example scripting/setup           "spack compiler rm gcc@12"
 example scripting/setup           "spack install hdf5"
 example scripting/setup           "spack install zlib%clang"
 

outputs/stacks.sh

@@ -15,7 +15,7 @@ spack compiler find
 example stacks/setup-0 "spack env create -d ."
 fake_example stacks/setup-0 "spack env activate ." ". /home/spack/spack/share/spack/setup-env.sh && spack env activate ."
 spack env activate .
-example stacks/setup-0 "spack add gcc@12.1.0 %gcc@11.3.0"
+example stacks/setup-0 "spack add gcc@12 %gcc@11"
 
 #cat "$project/stacks/examples/0.spack.stack.yaml" > spack.yaml
 
@@ -53,7 +53,7 @@ example stacks/view-0       "spack concretize"
 example stacks/view-0       "ls views/default"
 example stacks/view-0       "ls views/default/lib"
 example stacks/view-0       "ls views/full"
-example stacks/view-0       "ls views/full/gcc-12.1.0"
+example stacks/view-0       "ls views/full/gcc-12.3.0"
 
 cat "$project/stacks/examples/7.spack.stack.yaml" > spack.yaml
 
@@ -62,7 +62,7 @@ example stacks/view-1       "ls views/default"
 example stacks/view-1       "ls views/default/lib"
 example stacks/view-1       "ls views/full"
 
-example stacks/modules-0 "spack add lmod%gcc@11.3.0"
+example stacks/modules-0 "spack add lmod%gcc@11"
 example stacks/modules-0 "spack concretize"
 example stacks/modules-0 "spack install"
 

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

@@ -5,7 +5,7 @@
 spack:
   # add package specs to the `specs` list
   specs:
-  - gcc@=12.1.0%gcc@11.3.0
+  - gcc@12%gcc@11
   view: false
   concretizer:
     unify: true

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

@@ -13,7 +13,7 @@ spack:
     - serial_packages: [py-scipy]
 
   specs:
-  - gcc@=12.1.0%gcc@11.3.0
+  - gcc@12%gcc@11
   - matrix:
     - [$mpi_packages]
     - [$^mpis]

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

@@ -13,7 +13,7 @@ spack:
     - serial_packages: [py-scipy]
 
   specs:
-  - gcc@=12.1.0%gcc@11.3.0
+  - gcc@12%gcc@11
   - matrix:
     - [$mpi_packages]
     - [$^mpis]

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

@@ -13,7 +13,7 @@ spack:
     - serial_packages: [py-scipy]
 
   specs:
-  - gcc@=12.1.0%gcc@11.3.0
+  - gcc@12%gcc@11
   - matrix:
     - [$mpi_packages]
     - [$^mpis]

tutorial_basics.rst

@@ -370,7 +370,7 @@ added to the configuration.
 
 We can add GCC to Spack as an available compiler using the ``spack
 compiler add`` command. This will allow future packages to build with
-``gcc@12.1.0``. To avoid having to copy and paste GCC's path, we can use
+``gcc@12.3.0``. To avoid having to copy and paste GCC's path, we can use
 ``spack location -i`` to get the installation prefix.
 
 .. literalinclude:: outputs/basics/compiler-add-location.out

tutorial_configuration.rst

@@ -146,7 +146,7 @@ configuration file as follows:
 
    compilers::
    - compiler:
-       spec: gcc@11.3.0
+       spec: gcc@11.4.0
        paths:
          cc: /usr/bin/gcc
          cxx: /usr/bin/g++
@@ -180,7 +180,7 @@ level underneath the top-level 'spack' key. For example the above
      view: true
      compilers::
      - compiler:
-         spec: gcc@11.3.0
+         spec: gcc@11.4.0
          paths:
            cc: /usr/bin/gcc
            cxx: /usr/bin/g++
@@ -249,7 +249,7 @@ active environment):
        environment: {}
        extra_rpaths: []
    - compiler:
-       spec: gcc@11.3.0
+       spec: gcc@11.4.0
        paths:
          cc: /usr/bin/gcc
          cxx: /usr/bin/g++
@@ -311,14 +311,14 @@ We can verify that our new compiler works by invoking it now:
 
 
 This new compiler also works on Fortran codes. We'll show it by
-compiling a small package using as a build dependency ``cmake%gcc@11.3.0``
+compiling a small package using as a build dependency ``cmake%gcc@11.4.0``
 since it is already available in our binary cache:
 
 .. code-block:: console
 
-   $ spack install --reuse cmake %gcc@11.3.0
+   $ spack install --reuse cmake %gcc@11.4.0
    ...
-   $ spack install --no-cache --reuse json-fortran %clang@7.0.0-gfortran ^cmake%gcc@11.3.0
+   $ spack install --no-cache --reuse json-fortran %clang@7.0.0-gfortran ^cmake%gcc@11.4.0
    ...
 
 
@@ -573,7 +573,7 @@ this package and where it can be found:
          require: ~mpi
        perl:
          externals:
-         - spec: perl@5.26.1 %gcc@11.3.0
+         - spec: perl@5.26.1 %gcc@11.4.0
            prefix: /usr
 
 
@@ -614,7 +614,7 @@ not allowed to build its own Perl. We'll go with the latter.
          require: ~mpi
        perl:
          externals:
-         - spec: perl@5.26.1 %gcc@11.3.0
+         - spec: perl@5.26.1 %gcc@11.4.0
            prefix: /usr
          buildable: false
 
@@ -646,12 +646,12 @@ HDF5 to build with MPI by default again:
            mpi: [mpich, openmpi]
        perl:
          externals:
-         - spec: perl@5.26.1 %gcc@11.3.0
+         - spec: perl@5.26.1 %gcc@11.4.0
            prefix: /usr
          buildable: false
        mpich:
          externals:
-         - spec: mpich@3.3%gcc@11.3.0
+         - spec: mpich@3.3%gcc@11.4.0
            prefix: /usr
        mpi:
          buildable: false

tutorial_modules.rst

@@ -89,15 +89,15 @@ Add a new compiler
 The second step is to build a recent compiler. On first use, Spack
 scans the environment and automatically locates the compiler(s)
 already available on the system. For this tutorial, however, we want
-to use ``gcc@12.1.0``.
+to use ``gcc@12.3.0``.
 
 
 .. code-block:: console
 
-  $ spack install gcc@12.1.0
+  $ spack install gcc@12.3.0
 
 
-You can get this in your environment using ``spack load gcc@12.1.0``:
+You can get this in your environment using ``spack load gcc@12.3.0``:
 
 .. literalinclude:: outputs/modules/spack-load-gcc.out
    :language: console
@@ -113,7 +113,7 @@ To check which compilers are available you can use ``spack compiler list``:
 .. literalinclude:: outputs/modules/list-compiler.out
    :language: console
 
-Finally, when you confirmed ``gcc@12.1.0`` is properly registered, clean the environment
+Finally, when you confirmed ``gcc@12.3.0`` is properly registered, clean the environment
 with ``spack unload``:
 
 .. code-block:: console
@@ -343,7 +343,7 @@ Prevent some module files from being generated
 Another common request at many sites is to avoid exposing software that
 is only needed as an intermediate step when building a newer stack.
 Let's try to prevent the generation of
-module files for anything that is compiled with ``gcc@11.3.0`` (the OS provided compiler).
+module files for anything that is compiled with ``gcc@11.4.0`` (the OS provided compiler).
 
 To do this you should add the ``exclude`` keyword to ``${SPACK_ROOT}/etc/spack/modules.yaml``:
 
@@ -354,7 +354,7 @@ To do this you should add the ``exclude`` keyword to ``${SPACK_ROOT}/etc/spack/m
     default:
       tcl:
         exclude:
-        -  '%gcc@11.3.0'
+        -  '%gcc@11.4.0'
         all:
           filter:
             exclude_env_vars:
@@ -375,8 +375,8 @@ directory.
 
 
 if you look closely you'll see though that we went too far in
-excluding modules: the module for ``gcc@12.1.0`` disappeared as it was
-bootstrapped with ``gcc@11.3.0``. To specify exceptions to the ``exclude``
+excluding modules: the module for ``gcc@12.3.0`` disappeared as it was
+bootstrapped with ``gcc@11.4.0``. To specify exceptions to the ``exclude``
 rules you can use ``include``:
 
 .. code-block:: yaml
@@ -388,7 +388,7 @@ rules you can use ``include``:
         include:
         -  gcc
         exclude:
-        -  '%gcc@11.3.0'
+        -  '%gcc@11.4.0'
         all:
           filter:
             exclude_env_vars:
@@ -401,7 +401,7 @@ rules you can use ``include``:
 .. literalinclude:: outputs/modules/tcl-refresh-3.out
    :language: console
 
-you'll see that now the module for ``gcc@12.1.0`` has reappeared:
+you'll see that now the module for ``gcc@12.3.0`` has reappeared:
 
 .. literalinclude:: outputs/modules/module-avail-4.out
    :language: console
@@ -420,7 +420,7 @@ packages. In this case you only need to add the following line:
         include:
         -  gcc
         exclude:
-        -  '%gcc@11.3.0'
+        -  '%gcc@11.4.0'
         all:
           filter:
             exclude_env_vars:
@@ -449,7 +449,7 @@ use the ``hash_length`` keyword in the configuration file:
         include:
         -  gcc
         exclude:
-        -  '%gcc@11.3.0'
+        -  '%gcc@11.4.0'
         all:
           filter:
             exclude_env_vars:
@@ -483,7 +483,7 @@ the names are formatted to differentiate them:
         include:
         -  gcc
         exclude:
-        -  '%gcc@11.3.0'
+        -  '%gcc@11.4.0'
         all:
           conflict:
           - '{name}'
@@ -538,7 +538,7 @@ is installed. You can achieve this with Spack by adding an
         include:
         -  gcc
         exclude:
-        -  '%gcc@11.3.0'
+        -  '%gcc@11.4.0'
         all:
           conflict:
           - '{name}'
@@ -590,7 +590,7 @@ only certain packages. You can for instance apply modifications to the
         include:
         - gcc
         exclude:
-        - '%gcc@11.3.0'
+        - '%gcc@11'
         all:
           conflict:
           - '{name}'
@@ -642,7 +642,7 @@ directive and assigning it the value ``direct``:
         include:
         - gcc
         exclude:
-        - '%gcc@11.3.0'
+        - '%gcc@11'
         all:
           conflict:
           - '{name}'
@@ -750,7 +750,7 @@ After these modifications your configuration file should look like:
         include:
         - gcc
         exclude:
-        - '%gcc@11.3.0'
+        - '%gcc@11'
         all:
           filter:
             exclude_env_vars:
@@ -885,7 +885,7 @@ remove the remaining suffix projection for ``lapack``:
         include:
         - gcc
         exclude:
-        - '%gcc@11.3.0'
+        - '%gcc@11'
         all:
           filter:
             exclude_env_vars:
@@ -1046,7 +1046,7 @@ it's ``netlib-scalapack``:
       include:
         - gcc
       exclude:
-        - '%gcc@11.3.0'
+        - '%gcc@11'
         - readline
       all:
         filter:
@@ -1091,13 +1091,13 @@ the right e-mail address where to ask for it!
 Restore settings for future sections
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-For future sections of the tutorial, we will not use the ``gcc@12.1.0``
+For future sections of the tutorial, we will not use the ``gcc@12.3.0``
 compiler. Since it is currently the default compiler (our current
 default is the most recent version of gcc available), we will remove
 it now.
 
 .. code-block:: console
 
-  $ spack compiler rm gcc@12.1.0
+  $ spack compiler rm gcc@12.3.0
 
 This will ensure the rest of the tutorial goes smoothly for you.