CESM2 bug intel compiler

[stevenDH]

there appears to be a bug in the "config_compilers.xml" file in cesm2.0. The name of the MPI compilers used with the Intel compiler collection is wrong, as those are set to the names of the GNU compilers. This appears very odd to me, as these settings are wrong on any environment using the standard installation of the Intel compilers. I wonder what they do on cheyenne or other clusters to not have this issue. The part that is wrong starts on line 210, with the definition of the Intel compiler `<compiler COMPILER="intel">`. At the end of that group (line 248) you will see
[...]
<MPICC> mpicc </MPICC>
<MPICXX> mpicxx </MPICXX>
<MPIFC> mpif90 </MPIFC>
[...]
These three settings have to be changed to
[...]
<MPICC> mpiicc </MPICC>
<MPICXX> mpiicpc </MPICXX>
<MPIFC> mpiifort </MPIFC>
[...]

When changing these, I tested the build with a control case and it worked well. I wonder what the reason is to change the standard name of the Intel compilers and how is this handled on eg cheyenne which is compiled on intel if I am not mistaken. Anyone aware of this issue?

 

[sacks]

I believe this is machine dependent. On cheyenne, with intel modules loaded, mpif90 has the same meaning as mpiifort. Perhaps the machine you're using does not have the module environment set up the same way?