Adapt subdir for CUDA toolkit in host injections for 2025.06#64
Adapt subdir for CUDA toolkit in host injections for 2025.06#64casparvl wants to merge 27 commits intoEESSI:mainfrom
Conversation
…at it also doesnt include the CPU microarchitecture
…to e.g. /cvmfs/software.eessi.io/host_injections/x86_64, i.e. only include the CPU family in the prefix, not microarchitecture or accelerator architecture. Since these are binary installs, we don't need multiple copies, and requiring site admins to run the install scripts once per micro-architecture is just annoying (and requires more storage)
…DNN package was found in the old host-injections location (with micro-arch specific subdir). Also, adapt the path to search for the regular LmodError
…g to find /accel/accel/nvidia/ccXX. Fixed now to /accel/nvidia/ccXX
…eplaced (and would install in an outdated prefix)
… by the EESSI module, unless the installation directory already exists.
…ck file being added to software-layer-scripts
Co-authored-by: Kenneth Hoste <kenneth.hoste@ugent.be>
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws arch:zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Not sure if we'll ever deploy CUDA there, but, should make sure the scripts are at least up to date with what's in the bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion arch:aarch64/a64fx |
|
New job on instance
|
|
New job on instance
|
|
I marked this as draft, just to make clear that this shouldn't be merged (same changes + easystack file used to trigger rebuilds are included in #59, which will be merged) |
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws arch:zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Hmmm, now we'll get a mix of tarball names, with and without |
|
Replaced by #68 |
This PR mimics #59 , except that it does not add an EasyStack file, as no rebuilding is needed for 2025.06 (no CUDA was deployed yet).