-
Notifications
You must be signed in to change notification settings - Fork 0
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
FMS
fails to build with oneAPI
#3
Comments
Hi @manodeep , Use gitref
gitref
|
Thanks @harshula |
@harshula Would it be possible to add Related: Should the link flags append to any existing link flags - following the pattern of fortran flags? |
Hi @manodeep , FYI, the current FMS repository is a new fork of the upstream FMS repository. The As of last night, the new FMS repository's
I was able to successfully build access-fms using tag Please document any new compiler flags you want to use in |
Thanks @harshula. I am testing out the spack build for ESM1.6 - presumably the other failures will still occur. |
@harshula I still can't get
From the cmake error log (here:
This may be an Separately, would it be worthwhile to send through a PR to the ESM1.6 repo and have the |
Hi @manodeep , I used |
@harshula I am building directly on |
Hi @manodeep , You were able to compile it here: ACCESS-NRI/spack-config#54 (comment) |
Hahahahaha - thanks Harshula :D It must be that the packages are installable separately but not when part of the ESM1.6 |
The details for the build failure, when trying to build (as part of building
ESM1.6
) withspack
are captured in ACCESS-NRI/ACCESS-ESM1.6#46 (comment)The offending lines is here which raises a fatal error when the oneAPI compiler is used. Related to #1
The text was updated successfully, but these errors were encountered: