[Scons-users] Strange intel fortran compiler issue.

[Mats Wichmann]

On 10/30/24 09:49, Peter Diener via Scons-users wrote:
> Hi all,
> 
> I have just encountered a very perplexing issue with SCons when 
> compiling a Fortran code (with a few C++ files) on a Linux cluster I 
> have gotten access to.

> while I run scons -Q --tree=prune -n -f SConstruct.intel
> 
> I get:
> 
> Evaluating SConstruct.intel
> Evaluating module_sudoku.f90
> Evaluating reveal.f90
> Evaluating /sw/compiler/rrz-wrapper/oneapi-2024.2.1/ifx
> Evaluating reveal.x
> ifx -o reveal.x -g reveal.f90 module_sudoku.f90
> Evaluating .
> +-.
>    +-SConstruct.intel
>    +-module_sudoku.f90
>    +-reveal.f90
>    +-reveal.x
>      +-reveal.f90
>      +-module_sudoku.f90
>      +-/sw/compiler/rrz-wrapper/oneapi-2024.2.1/ifx
> 
> showing that scons does not find the dependency on the module.

not just the module, the object files are missing, too.

yes, this is odd looking.  don't actually expect the OneAPI compilers to 
work at all, there's a tracking issue on that - the whole OneAPI setup 
depends heavily on environment variables having been set, and you've 
only fixed for PATH - in kind of a brute-force way, by importing all of it.

There are some known issues with Fortran modules where the dependency is 
not built correctly, mainly if you're using a variantdir (which you're 
not). Since the same setup works on a different build host, that seems 
unlikely to be what you're running into.

Maybe 2024 got even stricter about needing certain env vars than 2022, 
but that shouldn't cause SCons to fail to build the tree, since that 
process doesn't involve invoking the compiler.