Frederic Tessier

@agsponer-metas thank you for the detailed investigation, this proves extremely valuable to track down this issue. I will first diff through your `.egslst` files; some default values for the transport...

No yet from my end.

There is an issue with the C compilation linking step: ``` CC = gcc C_FLAGS = -O2 Fortran compile OK C compile OK ld: warning: ignoring file c_conftest.o, building for...

@walleludvig can you share your `configure.log` file again? The other issue is `building for macOS-x86_64 but attempting to link with file built for unknown-arm64`, but I don't understand from your...

Oh wait, there was a mistake in my patch! Try this instead: ```diff diff --git a/HEN_HOUSE/scripts/configure b/HEN_HOUSE/scripts/configure index 810cf3b4..21bfc351 100755 --- a/HEN_HOUSE/scripts/configure +++ b/HEN_HOUSE/scripts/configure @@ -1490,6 +1490,12 @@ void JUNK_JUNK_()...

Ok, that is (very small) progress. I don't have an M1 on hand, so thanks for reporting quickly!

Ok never mind my patches, red herring. The issue seems to lie with the compiling target differences for the Fortran vs C conftest programs.

@walleludvig can you run `gfortran -v` and `gcc -v` and report what the `Target:` lines are?

So this explains the issue! `gcc` is building for `arm-64` and gfortran for `x86_64`. Linking those two objects does not work. I presume your `gcc` is in fact calling `clang`...

Thanks for trying that. There is still a mismatch with the targets, hugh: ``` ld: warning: ignoring file c_conftest.o, building for macOS-x86_64 but attempting to link with file built for...