-
Notifications
You must be signed in to change notification settings - Fork 701
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
WIP: {chem,phys}[GCCcore/11.3.0] ASAP3 v3.12.12, openkim-models v20210811, kim-api v2.3.0 w/ Python 3.10.4 #16355
base: develop
Are you sure you want to change the base?
WIP: {chem,phys}[GCCcore/11.3.0] ASAP3 v3.12.12, openkim-models v20210811, kim-api v2.3.0 w/ Python 3.10.4 #16355
Conversation
…2022a.eb, openkim-models-20210811-GCCcore-11.3.0.eb, kim-api-2.3.0-GCCcore-11.3.0.eb
@schiotz: Tests failed in GitHub Actions, see https://github.com/easybuilders/easybuild-easyconfigs/actions/runs/7673601287
bleep, bloop, I'm just a bot (boegelbot v20200716.01) |
Test report by @schiotz |
I am marking this as WIP for now, as I have to understand why kim-api is already present at the GCC level and not at GCCcore, and how to handle this for the intel toolchain version of Asap. |
@branfosj |
In In EasyBuild 5 we will detect and error if we find these (see easybuilders/easybuild-framework#4203). |
Thank you @branfosj I guess the reason I have not had problems with this that the Fortran files have only been used by openim-models which was also on GCCcore level, even if the resulting .so files were loaded into an Intel compiled Python module. I will play with this in the 2023a toolchain and come back to this PR once I have the details worked out. It should not be difficult. Once upon a time, the KIM API insisted on compiling with GCC even when building with the Intel toolchain in EasyBuild, but I think that was before they revamped their build system to use cmake. |
(created using
eb --new-pr
)