software-layer
software-layer copied to clipboard
EESSI
Software layer of the EESSI project
adding datasets yaml file, tarball creator and tree for scripts with WRF benchmark scripts
Python packages may use ctypes to load libraries: ``` cdll.LoadLibrary("libprotoc.so.3.13.0.0") ``` but this relies on the linker being able to find the libraries, which can fail in our current setup.
``` [ocaisa@gpunode1 gpu_support]$ which gcc /cvmfs/pilot.eessi-hpc.org/versions/2021.12/software/linux/x86_64/amd/zen2/software/GCCcore/10.3.0/bin/gcc [ocaisa@gpunode1 gpu_support]$ gcc -print-prog-name=ld ld ``` Doesn't this mean that GCC will just use whatever linker is in the path when compiling code? This...
Currently, the software layer is built on a host machine for that host machine (*i.e.* `--march=native`). However, on client side, we are potentially using those same binaries in a variety...
We should look into providing an `eessi-init` command that makes it easier/less awkward to initialize the EESSI environment. By default, it should simply run `source source /cvmfs/pilot.eessi-hpc.org/latest/init/bash`, but it could...
For some reason, when putting ``` source /cvmfs/pilot.eessi-hpc.org/versions/2021.12/init/bash ``` in my `.bashrc`, the environment succesfully initializes when I `ssh` somewhere, but it _fails_ to initialize in a job. My test...
Lots of European environments lack Neuro software. CC has EasyBuilds! Requested by malin at incf.org during the SORSE talk.
A script `bot-create-tarball.sh` could handle all environment settings etc and would thereby make the build script of the EESSI bot (`eessi-bot-build.slurm`) simpler. See original post by @boegel in https://github.com/EESSI/eessi-bot-software-layer/pull/10#discussion_r894927012
If we allow a default approach to where extensions to EESSI are stored `${EESSI_SOFTWARE_PATH/versions/host_injections}` (as is done in #172) then there is nothing to stop us shipping a module that...
Some software versions are getting a bit old, so we should update to a newer toolchain. `2020b` would be a good candidate (lots of easyconfigs available), but perhaps `2021a` or...