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
With the latest oneAPI compiler (and leaving netcdf and openmpi as is), I get the following error when I try to compile the oasis3-mct package. Same error also occurs upstream, but is not caught and the compile continues past this error. This happens because there is an extra -loopopt=0/1 option that is not correctly parsed and interpreted as a linking flag. The linker then looks for a non-existent file and borks.
Intel says this is an autoconf issue (see release notes for 2025 oneAPI) and can be fixed by using autoconf>=2.70 and using autoupdate. I have tried that but that does not fix the issue.
access-nri/oasis3-mct (from config.log in the build directory):
With the latest oneAPI compiler (and leaving netcdf and openmpi as is), I get the following error when I try to compile the
oasis3-mct
package. Same error also occurs upstream, but is not caught and the compile continues past this error. This happens because there is an extra-loopopt=0/1
option that is not correctly parsed and interpreted as a linking flag. The linker then looks for a non-existent file and borks.Intel says this is an
autoconf
issue (see release notes for 2025 oneAPI) and can be fixed by usingautoconf>=2.70
and using autoupdate. I have tried that but that does not fix the issue.access-nri/oasis3-mct (from
config.log
in the build directory):COSIMA/oasis3-mct: Same error in
config.log
but the build continues as demonstrated by the output frommake
:The text was updated successfully, but these errors were encountered: