-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial archdetect support for RISC-V and custom init script for RISC-V repo #568
Conversation
…io_GROMACS-2024.1
…io_GROMACS-2024.1
…o 2023.06-software.eessi.io_GROMACS-2024.1
…o 2023.06-software.eessi.io_GROMACS-2024.1
…io_GROMACS-2024.1
…:boegel/software-layer into 2023.06-software.eessi.io_GROMACS-2024.1
…'t want to be prevented from loading local CUDA modules because of the EESSI hook. See EESSI#523
…tensions in /home/casparl/eessi/...
…io_GROMACS-2024.1
add support for detecting zen4 in archspec
move OSU-Micro-Benchmarks 2023b to 2023b easystack
{2023.06,zen4}[system] EasyBuild v4.9.1
bumping scorecard-action version to 2.3.1
…l_modules Add possibility to ignore certain hooks on local modules
Instance
|
Instance
|
|
@bedroge Do we really need to introduce a separate Why can't we take an approach like we're doing for |
Since it's in a different repo, we need different init scripts etc. I don't think we can (easily) reuse all those files from the production repo? |
Right, ok.. I forgot about that part. |
You can override most of that stuff as a user/builder ( Edit: alternatively we could add a check to the production repo init scripts somewhere, and if it detects |
Maybe short-term, that makes sense, since to some extent |
I'm closing this PR and will open a new one with the aforementioned approach (changing the init scripts of the production repo, and let the redirect to |
The added spec file for RISC-V is still empty, and we may want to set
$cpu_flag_tag
to the right field whenever we want to differentiate between different RISC-V CPUs. But for now this does at least detect theriscv64
architecture, and it will just always fall back toriscv64/generic
, which is the only stack that we have anyway.