Skip to content

Commit fa07097

Browse files
authored
undo a few changes
1 parent d9a2309 commit fa07097

5 files changed

Lines changed: 2 additions & 10 deletions

tutorial_buildsystems.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,7 @@ If we look inside, we see that ``CC`` and ``CXX`` point to our GNU compiler:
238238
239239
.. note::
240240
As usual make sure you have shell support activated with Spack:
241-
``source /path/to/spack_root/share/spack/setup-env.sh``
241+
``source /path/to/spack/share/spack/setup-env.sh``
242242

243243
.. code-block:: console
244244

tutorial_configuration.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -813,5 +813,3 @@ For more detailed documentation on Spack's many configuration settings, see `the
813813

814814
For examples of how other sites configure Spack, see https://github.com/spack/spack-configs.
815815
If you use Spack at your site and want to share your config files, feel free to submit a pull request!
816-
817-
[end of tutorial_configuration.rst]

tutorial_developer_workflows.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -328,5 +328,3 @@ While we won't build out this example it illustrates how the ``dev_path`` for ``
328328
Now if we want to do most of our incremental builds using the ``Release`` build and periodically check the results using the ``Debug`` build we can combine the workflow from the previous example: dive into the ``Release`` versions build environment using ``spack build-env scr build_type=Release -- bash`` and navigate with ``spack cd -b scr build_type=Release``.
329329
Note that since there are two ``scr`` specs in the environment we must distinguish which one we want for these commands.
330330
When we are ready to check our changes for the debug build, we can exit out of the build environment subshell, rerun ``spack install`` to rebuild everything, and then inspect the debug build through our method of choice.
331-
332-
[end of tutorial_developer_workflows.rst]

tutorial_modules.rst

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Now we can re-source the setup file, and Spack modules will be put in our module
6565

6666
.. code-block:: console
6767
68-
$ . share/spack/setup-env.sh
68+
$ . spack/share/spack/setup-env.sh
6969
7070
.. FIXME: this needs bootstrap support for ``lmod``
7171
@@ -987,5 +987,3 @@ Since it is currently the default compiler (our current default is the most rece
987987
$ spack compiler rm gcc@12.3.0
988988
989989
This will ensure the rest of the tutorial goes smoothly for you.
990-
991-
[end of tutorial_modules.rst]

tutorial_packaging.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -692,5 +692,3 @@ Making a package externally detectable
692692
* `Making a package externally discoverable
693693
<https://spack.readthedocs.io/en/latest/packaging_guide.html#making-a-package-discoverable-with-spack-external-find>`_:
694694
for making a package discoverable using the ``spack external find`` command
695-
696-
[end of tutorial_packaging.rst]

0 commit comments

Comments
 (0)