Dan Williams

I'll just add that when I was testing this locally it seems to only be reproducible when running a parallel build with `-jN`. A serial build would do things in...

Yeah, fair enough. Even for the parallel builds I'll add that it would sometimes work, sometimes not. I wonder since it seems to be a windows specific thing then is...

> How are you creating your Environment()? Specifically are you setting `FORTRANSUFFIXES` (or any of the `F*SUFFIXES` env vars)? We definitely do *not* configure that particular variable currently. We do...

The library in question has a combination of both `.f90` and `.f` suffixes since it includes F90 free format and F77 fixed format code.

Right, the library in question uses both dialects because it links in an older code base shared with other applications. So, definitely useful to us. One issue though is that...

Yes, we have a modified version of ifort.py. Staring at the differences with your current code the diffs are: - It configures msvc tool if needed. This could maybe be...

Based on my hypothesis I tried to reproduce this with a simple example, could not do it yet....

Yeah sure. I’ll push it up later today and share a PR.

Regarding the file extensions there is this: https://www.intel.com/content/www/us/en/develop/documentation/fortran-compiler-oneapi-dev-guide-and-reference/top/compiler-setup/use-the-command-line/file-extensions.html So, Intel does seem to accept `.i` and `.i90` as acceptable file extensions where those files are passed to the compiler.

lol. Yeah, it's not the easiest to navigate or digest it. Here's the ifort tool module we are using currently: https://github.com/dnwillia-work/scons/pull/1