You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our EB recipes for Intel compilers and PGI split the installed files into a "restricted" and a "public" location, with only the latter being distributed.
In order to get working compilers in places where they don't have access to the restricted repository, providing EB recipes to install those bits locally is needed.
Issue #11 allows for locally installed software to mesh with our central stack, so it should only be a matter of making the install location of the restricted bits configurable to allow both a split and a unified installation.
Just letting you know that there might be interest on our side for this. As you know, we will be deploying the CC stack on our cluster, and researchers have been showing interest in procuring the Intel compiler suite.
Currently, our EB recipes for Intel compilers and PGI split the installed files into a "restricted" and a "public" location, with only the latter being distributed.
In order to get working compilers in places where they don't have access to the restricted repository, providing EB recipes to install those bits locally is needed.
Issue #11 allows for locally installed software to mesh with our central stack, so it should only be a matter of making the install location of the restricted bits configurable to allow both a split and a unified installation.
This is probably doable by modifying the
postinstallcmds
in our hookshttps://github.com/ComputeCanada/easybuild-computecanada-config/blob/master/cc_hooks_gentoo.py#L146
The text was updated successfully, but these errors were encountered: