-
Notifications
You must be signed in to change notification settings - Fork 15
only use $EESSI_VERSION in init/eessi_defaults
#116
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
Conversation
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
trz42
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
|
Tarballs have been ingested. |
I think I had a good reason to use
$EESSI_VERSION_DEFAULTin the RISC-V if statement, but that's now giving me issues: theEESSI-install-software.shscript sources this file from the git repo, and then__EESSI_VERSION_DEFAULT__is not replaced by an actual value. This leads to paths likeEESSI_COMPAT_LAYER_DIR=/cvmfs/software.eessi.io/versions/__EESSI_VERSION_DEFAULT__/compat/linux/riscv64.Instead, I'm now just setting
$EESSI_VERSIONnear the top, and then use it everywhere.