I noticed a change of behavior of the following scenario between [email protected] and spack@develop :
$ module load gcc/8.1.0
$ spack compiler find
On "release" tag v0.12.1, the compiler is found, on the develop branch, it isn鈥檛.
The issue occurs on a supercomputer using lmod mechanism for modules.
@alalazo FYI (although I can look into this if you prefer)
Bisect is implicating https://github.com/spack/spack/pull/10190 (https://github.com/spack/spack/commit/6d56d4545472ddff1cdc0e8fd49d8260428a141e)
I'm not sure why that would cause an error yet.
@adrienbernede @scheibelp I'll have a look at this today, thanks for the report
I confirm that the problem is now solved.
Thank you
Most helpful comment
I confirm that the problem is now solved.
Thank you