I would like to test some of the already available ComIn-plugins for additional output capabilities and therefore rebuilding ICON with Comin enabled. But the build failed. I than tried to build ICON without Comin, and this also failed.
The following steps were tested to remove possible user errors:
disable conda environment
empty .bashrc and .bash_profile
clone icon/icon-model 2025.10-public release into new icon-model2 instead of the previous used icon/icon-model 2024.10-public
tested with both levante.intel and levante.gcc configure script.
Minimal steps that reproduced this error for me:
git clone git@gitlab.dkrz.de:icon/icon-model.git icon-model2
cd icon-model2
git submodule update --init
cd ..
mkdir icon-comin2
cd icon-comin2
../icon-model2/config/dkrz/levante.intel --disable-art --disable-jsbach --disable-quincy
make -j 16
output:
configure: WARNING: Failed to run MPI programs
configure: error: in `/home/b/b383631/workspace/model/icon/icon-comin2/externals/yaxt':
configure: error: unable to find a working MPI launch program, which is
required for checks for known MPI defects (see --without-regard-for-quality)
See `config.log' for more details
make[1]: *** [icon.mk:754: externals/yaxt/Makefile] Error 1
make[1]: Leaving directory '/work/bb1376/user/kolja/model/icon/icon-comin2'
maybe that is just a typo - but to be sure: you’re doing a git clone into icon-model2, but then you are changing to the directory icon-comin2 (where also the error is happening).
git clone git@gitlab.dkrz.de:icon/icon-model.git icon-model2
git submodule update --init
cd ../icon-comin2```
Your directory structure is a little bit confusing but if you clone the model into icon-model2 then you should first cd into that directory and then update the git submodules within it. Or just do
I replicated the exact commands you posted above and it worked for me.
I noticed in your error message, however, that you are in /work/bb1376/user/kolja/model/icon/icon-comin2 but that the error actually comes from /home/b/b383631/workspace/model/icon/icon-comin2/externals/yaxt in your home directory. Actually, your top config.log in icon-comin2 in /work calls /home/b/b383631/workspace/model/icon/icon-model2/configure. I can’t look into your home directory but since you cloned and configure/make the model in your /work directory there should not be anything called in your /home.
this didnt solve it (but maybe part of it). What I assume was the difference between my and your call was, that I had used an interactive session as written in the comin documentation for the build process.
salloc -A<project> -pinteractive
While my personal issue is solved, does this happen for others as well?