Required before Spack can work in a practical sense. In theory, Spack doesn’t need any additional installation justĭownload and run! But in real life, additional steps are usually Sourcing time, ensuring future invocations of the spack command willĬontinue to use the same consistent python version regardless of changes in Setup script, SPACK_PYTHON will be set to the interpreter found at Python interpreter to use, which can be explicitly overridden by setting When the spack command is executed it searches for an appropriate The spack command directly from spack/bin/spack. If you do not want to use Spack’s shell support, you can always just run MODULEPATH manually instead, you can set the SPACK_SKIP_MODULESĮnvironment variable to skip this step and speed up sourcing the file. On shared filesystems, this can be a bit slow,Įspecially if you log in frequently. In order to know which directory to add to your MODULEPATH, these scripts Up your MODULEPATH to use Spack’s packages, and add other usefulīash and zsh, it also sets up tab completion. Sourcing these files will put the spack command in your PATH, set Working on which systems is planned but not yet available.
A build matrix showing which packages are These requirements can be easily installed on most modern Linux systems Spack has the following minimum system requirements, which are assumed toīe present on the machine where Spack is run: System prerequisites for Spack ¶