software-layer
software-layer copied to clipboard
EESSI
Software layer of the EESSI project
``` 83 out of 303 required modules missing: * gawk/5.3.0-GCC-12.3.0 (gawk-5.3.0-GCC-12.3.0.eb) * mm-common/1.0.6-GCCcore-12.3.0 (mm-common-1.0.6-GCCcore-12.3.0.eb) * sparsehash/2.0.4-GCCcore-12.3.0 (sparsehash-2.0.4-GCCcore-12.3.0.eb) * libsigc++/3.6.0-GCCcore-12.3.0 (libsigc++-3.6.0-GCCcore-12.3.0.eb) * Boost.Python/1.82.0-GCC-12.3.0 (Boost.Python-1.82.0-GCC-12.3.0.eb) * tqdm/4.66.1-GCCcore-12.3.0 (tqdm-4.66.1-GCCcore-12.3.0.eb) * PyCairo/1.25.0-GCCcore-12.3.0 (PyCairo-1.25.0-GCCcore-12.3.0.eb) *...
Currently, all software for a given CPU microarchitecture is installed under the same `EASYBUILD_INSTALLPATH`. For supporting builds which include GPU-accelerated software we want to install these into sub-directories where each...
once https://github.com/archspec/archspec/pull/53 is merged, `eessi_software_subdir_for_host.py` will need to be slightly modified because archspec in some circunstances will detect a `generic` architecture (e.g. `x86_64_v3`) with a `generic` vendor string, which will...
Should we enable support for this in EESSI, it will be disabled by default via https://github.com/easybuilders/easybuild-easyconfigs/pull/12854 (and we currently do not have support for it)
While working on #86, I noticed that the `module avail ` command always returned 0 for me, even if a module for `` does not exist: ``` [EESSI pilot 2021.03]...
If these two PRs can be deployed & merged first, then this PR could also be built for A64FX: * https://github.com/EESSI/software-layer/pull/786 * https://github.com/EESSI/software-layer/pull/787
I'm using this PR to verify that the changes made for support builds for `dev.eessi.io` don't cause trouble for the `software.eessi.io` builds, so it sits on top of: * #771...