Support intel-compiler-llvm (oneapi) compilers

[harshula]

https://forum.access-hive.org.au/t/how-to-build-access-om2-on-gadi-using-intel-oneapi-compilers/1574/1

[access-hive-bot]

This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/how-to-build-access-om2-on-gadi-using-intel-oneapi-compilers/1574/3

[harshula]

Notes

https://www.intel.com/content/www/us/en/developer/articles/guide/porting-guide-for-ifort-to-ifx.html

[harshula]

Status: IFX internal compiler errors occur. e.g. #101 (comment)

[penguian]

Intel has discontinued the ifort compiler as at Intel OneAPI 2025.
See the Release Notes, Developer Guide and Reference and the updated Porting Guide.

[harshula]

Thanks @penguian , @manodeep had a chat with me before the holidays and said he was going to look into the state of IFX. I opened ACCESS-NRI/ACCESS-OM2#93.

[manodeep]

Thanks Harshula. Yes, I have been looking into compiling the packages with with oneAPI compilers - so far without success, at least within spack. I am currently building from git source directly (oasis3-mct right now) but running into strange configure error with ifx. Building with the latest classic intel compiler (2021.10.0), with all of the optimisation flags turned on, works fine.

[manodeep]

Thanks for the Release Notes link Paul - that shows the autoconf error that I am seeing when swapping out the classic with the oneAPI compilers in the section "Configure Script Reports: "linking to Fortran libraries from C fails".

(Unfortunately, the suggested fix did not work for me, even after loading the latest autoconf module on NCI)