./setup --extra-fc-flags="…" not propagated to the compiler call

[reut...@gmail.com]

Hi,

newer versions of gfortran often need an extra flag "-fallow-argument-mismatch" as the former warning about a type mismatch is now treated as an error. Hence I issued:

./setup --extra-fc-flags="-fallow-argument-mismatch" …

I still got the "Error: Type mismatch between actual argument at (1)…" during compilation of Dirac. As I wondered whether this extra flag was proper propagated to the gfortran call, I used a small wrapper to gfortran:

#!/bin/sh
MYDIR=$(dirname $(readlink -f "$0"))
"$MYDIR/gfortran_real" -fallow-argument-mismatch $*

and this converted the above error into a warning and the compilation succeeded. My conclusion is, that the "--extra-fc-flags=…" seems to be recorded in build/CMakeCache.txt but not be used later on.

-- Reuti

[Visscher, L. (Luuk)]

Dear Reuti,

Thanks for your reports on this. We plan to work on an overhaul of the DIRAC cmake code during our summer meeting. 

For this it would be helpful to see more details of what the setup script is printing. Can you make a new issue for this on our gitlab repository (https://gitlab.com/dirac/dirac/-/issues) 

and upload the output of the setup script there ? This will make it easier to track what is going on and find a solution.

Thought we had already added this "-fallow-argument-mismatch" flag in cmake for instance, but apparently something goes wrong there. Depending on where this occurs, it could be related to

the fact that some modules (in particular ExaTensor) still have an independent build system (did not get around fixing this in time, there is already an issue for this).

best regards,

Luuk

--
You received this message because you are subscribed to the Google Groups "dirac-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dirac-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dirac-users/d98b8fa3-936e-4a10-ad26-c2d0e2815bfdn%40googlegroups.com.

[peterso...@gmail.com]

Dear Luuk,

 

Not sure if this is fixed in Dirac 2025, but still in Dirac 2024 I needed to add this argument to build/external/pelib-build/CMakeCache.txt

 

Best regards,

 

-Kirk

 

To view this discussion visit https://groups.google.com/d/msgid/dirac-users/5144D83C-B6F2-4954-9580-E25DDC86E2F5%40vu.nl.

[reut...@gmail.com]

Hi Kirk,

Thx for the hint. Adding this argument to build/external/pelib-build/CMakeCache.txt does indeed solves the problem too.

-- Reuti