Dom Heinzeller

@arunchawla-NOAA I declared defeat over that question a while ago.

Here is a list of issues that I think are related, and I agree it has to do with numpy: - https://github.com/spack/spack/issues/8616 - https://github.com/numpy/numpy/issues/14146 - https://github.com/numpy/numpy/pull/13132 - https://github.com/spack/spack/pull/12170 - https://github.com/spack/spack/issues/10361...

Thank you both for looking at this. I was going in a similar direction, albeit not in the spack framework itself, but in the packages. I'll better wait for you...

> > The problem is that during the py-scipy install it uses `ifort` as Fortran compiler because of > > https://github.com/spack/spack/blob/d8e566d5542e2c8f0508a83922ba1eada5d473cd/var/spack/repos/builtin/packages/py-scipy/package.py#L124 > > This is probably a bug in the...

All that I did was create an environment configured to use the Intel compiler, add spack ***@***.*** to it and ran “spack concretize” and “spack -ddd install -v”. This is...

@adamjstewart I am looking at a dirty workaround for now, because I need to get this working asap. Wondering if I can get the complete linker flags from the spack...

> #32767 This is certainly part of the solution, but I tried this for both py-numpy and py-scipy (https://github.com/spack/spack/issues/32732#issuecomment-1254106020) and it didn't help. I still got the gfortran in the...

> #32767 I'll try again. I didn't have the switch between x86 and x86_64 when I tried a similar solution a few days ago.

@DarylGrunau Thanks a lot, your PR also solved the problem on my system. I noticed that the difference between what I tried (based on what was in develop) and your...

This issue will be fixed in https://github.com/spack/spack/pull/32767