software-layer
software-layer copied to clipboard
Software layer of the EESSI project
I think we should deploy the script from https://github.com/EESSI/software-layer-scripts/pull/120 through this current PR, then change the `build.sh` back to it's original form. The issue is that https://github.com/EESSI/software-layer-scripts/pull/120 can't be deployed...
An older version for 2023.06 failed to build due to Qt6 issues (see #800), but we do already have Qt6 for 2025a, so let's try this one instead.
When ingesting `Boost.MPI` from #1279 we noticed that the `x86_64` builds have 16 more files than the `aarch64` builds. @bedroge checked the tarballs and compared them with each other and...
We use CI matrices for all of the different architectures, which is creating a lot of CI jobs. Do we really need to do this though? With the `EESSI` module...
When including software in the EESSI stack, we should not only ensure that the software can be built on the various archs, but also that `--module-only` returns an identical set...
We saw failing sanity check in https://github.com/EESSI/software-layer/pull/1190. ``` >> CUDA sanity check summary report: >> Number of CUDA files checked: 128 >> Number of files missing one or more CUDA...
``` 1 out of 1 required modules missing: * code-server/4.100.2 (code-server-4.100.2.eb) ```