Compiler names passed to the testing framework should a) correspond to actual compiler names (gfortran) or b) at least the general suite name used by modules (gnu) and if an invalid item is supplied, the failure in ./configure should be caught instead of letting things fail in byzantine ways later.
Current Behavior
Using gfortran as the compiler name will appear to work at first, but this is passed part-and-parcel to the configure script, which expects gfort and fails (silently, in this case) and then compilation fails later.
Possible Solution
Rename run_tests.py command line option from compiler to configure type or somesuch, or have a reasonable mapping between common compiler names and what configure expects. OR, barring that, catch the error and fail fast with a informative error.
Expected Behavior
Compiler names passed to the testing framework should a) correspond to actual compiler names (
gfortran) or b) at least the general suite name used by modules (gnu) and if an invalid item is supplied, the failure in./configureshould be caught instead of letting things fail in byzantine ways later.Current Behavior
Using
gfortranas the compiler name will appear to work at first, but this is passed part-and-parcel to theconfigurescript, which expectsgfortand fails (silently, in this case) and then compilation fails later.Possible Solution
Rename
run_tests.pycommand line option fromcompilertoconfigure typeor somesuch, or have a reasonable mapping between common compiler names and whatconfigureexpects. OR, barring that, catch the error and fail fast with a informative error.Steps to Reproduce (for bugs)
run_tests.pywith--compiler gfortran