Building error of mksurfdat

[InneVanderkelen]

Hello,

I am building the new mksurfdata_esmf tool, provided in the ctsm5.2.mksurfdata branch on our machine Piz daint, following the instructions layed out in the Readme here: CTSM/tools/mksurfdata_esmf at ctsm5.2.mksurfdata · ESCOMP/CTSM.


When building the tool, I manually export the COMPILER=gnu
In addition, the LD_LIBRARY_PATH environmental variable contains the paths to the netcdf-c and netcdf-fortran packages. And the ESMF_PATH to the esmf package.
These settings make that the port can successfully compile and run CTSM with the NUOCP driver.

After cloning the branch and checking out the externals, I issue

cd tools/mksurfdata_esmf/
./gen_mksurfdata_build.sh -m pizdaint -v

This gives the following error message:

[daint101:~/ctsm5.2.mksurfdata/tools/mksurfdata_esmf]$ ./gen_mksurfdata_build.sh -m pizdaint -v
cime Machine is: pizdaint...
Run cime configure for machine pizdaint...
configure for the default MPI-library and compiler...
COMPILER = gnu, MPILIB = mpich, DEBUG = FALSE, OS = CNL
Do the cmake build...
CMake Error at /usr/share/cmake/Modules/CMakeDetermineFortranCompiler.cmake:33 (message):
  Could not find compiler set in environment variable FC:

  mpif90.
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)


CMake Error: CMAKE_Fortran_COMPILER not set, after EnableLanguage
-- Configuring incomplete, errors occurred!
See also "/users/ivanderk/ctsm5.2.mksurfdata/tools/mksurfdata_esmf/tool_bld/CMakeFiles/CMakeOutput.log".
Error doing cmake for pizdaint mpich gnu

Attached are the config machine and compilers xml files, which are saved in .cime.

Do you have any idea how I could solve this issue?
Please let me know if more information is needed. Many thanks in advance!

 

[slevis]

@erik do you have thoughts on this? I'm afraid the build part of the tool is not my forte...

 

[slevis]

@jedwards any thoughts on this one?

@InneVanderkelen in the meanwhile, you should have better luck on cheyenne, casper, or izumi (if you have access) where this build script has worked successfully.

 

[jedwards]

Typically on a cray system FC should be set to ftn and not mpif90.

 

[InneVanderkelen]

Thanks both Sam and Jim for your replies.

I tried to set FC to ftn, both manually with an export command and in the config_compilers.xml as below.

<compiler MACH="pizdaint" COMPILER="gnu">
 <FC> ftn </FC>
</compiler>

However, the error remains the same. Does this variable needs to be hardcoded in the build script somewhere?

@slevis I am using the tool on Cheyenne, but we want to have a more sustainable solution for my other group members who don't have access to cheyenne.