OpenIFS not compiling: don't know how to build specified target

[alxthor]

I am using esm tools installed with direnv on Levante. 1 year ago I was able to do esm_master get-awicm3-v3.1 and esm_master comp-awicm3-v3.1. Now neither this nor esm_master install-awicm3-v3.1 works any more. Models are dowloaded fine. OASIS and XIOS compile without problem, but openIFS compilation exits with

[done] make dest-init      # 0.0s
[init] make oifs           # 2026-02-12T15:31:48Z
[info] sources: total=0, analysed=0, elapsed-time=0.1s, total-time=0.0s
[FAIL] make oifs           # 0.2s
[FAIL] make                # 0.3s
[FAIL] master.exe: don't know how to build specified target

Neither my version of esm tools nor the direnv was actively changed by me.
It seems like something in the environment has changed over time.
Documenting this issue here, in case this happens to someone else in the future.

[mandresm]

Do you have more specific dates?

XIOS in version 3.1 of AWICM3 points to a branch master that has changes in February 2025
RNFMAP is also in a branchg awicm3-frontiers-freeze-candidate-1 with changes on January 2025

If this changes happen after the last time you compiled the model, those changes could be introducing the problem (although I doubt it). The other components are tagged so the other components should be the same as your compilation one year ago.

Changes in the environment are possible, it would be worth checking in the comp scripts whether you have a module load whose version is not pinned. If there is anything not pinned that could be another point where a change might have be introduced.

I had a successful comp and run with 3.1.1 in levante on 21.01.2026, not the same version to yours but pretty close.

A change on the environment might be the issue but we should be able to trouble shoot what is going wrong with the compilation. Can you share a path to the log of the compilation?

[alxthor]

It definitely worked on 05.02.25 using esm_master get-awicm3-v3.1 and then esm_master comp-awicm3-v3.1. On 14.03.25 at least still ./comp-oifs-43r3-awicm-3.1_script.sh worked. So basically these changes should not have affected it, I guess.

I don't see any untagged module load in the comp-oifs-43r3-awicm-3.1_script.sh.

@JanStreffing was able to compile v3.1 today on Levante, however on a different esm-tools branch than me and on albedo using virtually the same esm-tools branch as me, both without using direnv. This maybe points to an uexpected change in the environment which might not be easy to find. Fixing this issue is also not critical to me. I can live with the binaries I compiled last year. Not being able to recompile is just a bit inconvenient as I basically wanted to include a small change which would have been nice.

I compiled in /home/a/a270205/esm_tools_v6.35.0/model_codes (I renamed the awicm3 directory to awicm3-v3.1_OIFS-COMP-ERROR). The output from esm_master install-awicm3-v3.1 can be found in /home/a/a270205/esm_tools_v6.35.0/model_codes/OIFS-COMP_ERROR.log

[mandresm]

Hi @alxthor, I understand you strongly suspect about the environment. Still, I am happy to check at the compilation log.

The problem I have with /home/a/a270205/esm_tools_v6.35.0/model_codes/OIFS-COMP_ERROR.log is that I see not error messages, only the [FAIL]. Is it possible that you have not dumped the stderr in the log file? Aka, have you run the comp-command with?

esm_master install-awicm3-v3.1 > OIFS-COMP_ERROR.log  2>&1

[alxthor]

In fact, I just ran the command without any redirection and manually copied the output on screen to a file afterwards. But that should include both stdout and stderr, shouldn't it?

But I can also run it again with proper output redirection

[mandresm]

That should indeed have both... so strange. I'll have a look at it again on monday