Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tweak spack docs for polaris to indicate users should use soft #494

Merged
merged 6 commits into from
Oct 17, 2024
Merged

Tweak spack docs for polaris to indicate users should use soft #494

Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
7981ea6
tweak Spack docs for polaris to indicated users should use /soft
Oct 17, 2024
1a655ed
fix branch
Oct 17, 2024
11c0c86
fix formatting
Oct 17, 2024
3f5a14a
fix wording
Oct 17, 2024
d704f02
fix formatting
Oct 17, 2024
3178831
fix wording
Oct 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions docs/polaris/applications-and-libraries/libraries/spack-pe.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@
Spack is an HPC-oriented package manager which ALCF uses to install software for
the user environment.

Users should not depend on libraries present in the system, but instead load
them from `/soft` using Spack as described below.
koysean marked this conversation as resolved.
Show resolved Hide resolved

ALCF's Spack PE is a Spack-managed software stack which provides various build
tools, utilities, and libraries. It consists of a base stack (`spack-pe-base`)
and PrgEnv-dependent stacks (currently `spack-pe-gnu`).
Expand All @@ -23,14 +26,14 @@ The base suite of software tools and libraries can be accessed by loading the
numerous modules.

For example, to load `cmake` starting from the default environment, a user
should run the following commands:
```
module use /soft/modulefiles
module load spack-pe-base
module load cmake
```
should run the following commands: ``` module use /soft/modulefiles module load
spack-pe-base module load cmake ```

The `spack-pe-base` module adds paths to the user's `MODULEPATH`; individual packages are subsequently loaded through the newly available modules. The full list of available packages can be viewed by running `module avail` or `module --show-hidden avail` for a complete listing. Packages are loaded in the same way from `spack-pe-gnu`.
The `spack-pe-base` module adds paths to the user's `MODULEPATH`; individual
packages are subsequently loaded through the newly available modules. The full
list of available packages can be viewed by running `module avail` or `module
--show-hidden avail` for a complete listing. Packages are loaded in the same way
from `spack-pe-gnu`.


## Inspecting packages
Expand All @@ -40,12 +43,9 @@ updated to integrate the package into the user's environment. Additionally, the
`PACKAGE_ROOT` variable is set to the path to the installation prefix of the
package. For example, after loading `cmake` as above:

```
$ echo $CMAKE_ROOT
``` $ echo $CMAKE_ROOT
/soft/spack/gcc/0.6.1/install/linux-sles15-x86_64/gcc-12.3.0/cmake-3.27.7-a435jtzvweeos2es6enirbxdjdqhqgdp/
$ ls -a $CMAKE_ROOT
. .. bin doc share .spack
```
$ ls -a $CMAKE_ROOT . .. bin doc share .spack ```

This variable can be used to inspect software installations and find header or
library paths. Additionally, Spack packages have a `.spack` directory in the
Expand Down
Loading