Building UM executable using ESMF library with fcm_make fails

Technical
4

Hi @Paul.Gregory,
the CM3 build uses several modules created by spack using the configuration file here. When loaded, these modules export several paths for each dependency required in the build:

  modules:
      prefix_inspections:
        bin:
         - PATH
        lib:
         - LIBRARY_PATH
         - LD_LIBRARY_PATH
        lib64:
         - LIBRARY_PATH
         - LD_LIBRARY_PATH
        include:
         - FPATH

We’re working on transitioning to a full spack build, which will hopefully be a bit more robust and avoid steps like this. For the meantime as a workaround, could you test if manually exporting LIBRARY_PATH with the path for your version of ESMF helps with the fcm_make step?