This topic is now DEPRECATED. Instead see [image] ACCESS-NRI Spack Cheat Sheet spack ACCESS-NRI Spack Cheat Sheet This document focuses on Spack v1 and newer. The latest version of Spack, maintained by ACCESS-NRI, can be loaded by running: module use /g/da…

[image] Aidan: Apparently build parallelism is possible by generating dependency Makefiles and using make level parallelism This is an example of it being used in production https://github.com/BlueBrain/spack/blob/up-the-stream/bluebrain/deployment/gitlab-ci.yml#L213-L221

If you want to update a spack package with the latest versions spack checksum is your friend From: https://spack.readthedocs.io/en/latest/packaging_guide.html#spack-checksum If you want to add new versions to a package you’ve already created, this is automated with the spack checksum command. Her…

Want to find out what packages depend on an installed package? spack dependents --installed packagename/hash (from Slack )

Installing Perl package in Spack with an old Intel compiler (2019.5.281) You may need: --- a/var/spack/repos/builtin/packages/perl/package.py +++ b/var/spack/repos/builtin/packages/perl/package.py @@ -179,6 +179,10 @@ def patch(self): os.chmod("lib/perlbug.t", 0o644) filter_file…

If you get this non-obvious error: $ spack install openmpi@4.0.2 target=x86_64 ==> Error: Cannot find valid provider for virtual pkgconfig Updating the compilers solved it: $ spack compiler find ==> Added 2 new compilers to /home/harshula/.spack/linux/compilers.yaml gcc@12.2.0 gcc@11.3.0

Useful way to uninstall all packages for a particular platform: $ spack uninstall --all arch=linux-debianbookworm-x86_64

You may need to make the following change to use target=x86_64: --- a/etc/spack/defaults/concretizer.yaml +++ b/etc/spack/defaults/concretizer.yaml @@ -25,7 +25,7 @@ concretizer: # microarchitectures. Valid values are: "microarchitectures" or "generic". # An example of "microarchitectures…

I just saw Spack convert compiler version 2019.5.281 to 19.0.5.281: $ module load intel-compiler/2019.5.281 $ spack compilers ==> Available compilers -- clang rocky8-x86_64 ------------------------------------------ clang@14.0.6 -- gcc rocky8-x86_64 -------------------------------------------- gcc…

Before I forget, I contacted someone who’d used spack on gadi and he said A shared spack installation will not work correctly on the /g/data filesystem, since POSIX file locking is disabled for lustre mounts on gadi (see the Spack documentation here on why this is needed: https://spack.readthedoc…

@Aidan Thanks for the info. I think this is fine for the COSIMA spack instance on /g/data/ik11, as few people have write access and we don’t install things very often. At least I’ve not encountered any problem up to now.

Random spack errors/tips/fixes

Technical spack

Topic		Replies	Views
Initial experiments with spack spack spack , compile	17	645	6 December 2022
Building ACCESS-OM2 on Archer2 (UK HPC) spack spack , access-om2	54	759	13 March 2026
Shared access spack configuration spack python , spack	33	1593	3 April 2025
Questions for Spack meeting spack	34	893	28 May 2026
How to create a Docker container to build ACCESS-OM2 (x86) spack spack	2	307	18 September 2023

Random spack errors/tips/fixes

Related topics