path: root/reproduce/software/make
diff options
authorBoud Roukema <boud@cosmo.torun.pl>2020-08-08 17:58:03 +0200
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2020-08-08 18:40:38 +0100
commitd3739931e1662d1476988badb3305e53b0355cda (patch)
treec72a8c3ebdb6352ab92ea06f86cfe30ff7136f63 /reproduce/software/make
parent32f3ba14f6c6efcef7edea0a365638527721f509 (diff)
Configuration fail if gfortran necessary, but not built or available
When the host C compiler is used (either by calling '--host-cc' or on OSs that we can't build the GNU C Compiler), Maneage will also not build the Fortran compiler 'gfortran'. Until now, the './project configure' script would give a big warning about the need for 'gfortran' and the fact that it is missing, and would for 5 seconds, but it would continue anyway. For projects that don't need 'gfortran', this can be confusing to the users and for those that need 'gfortran', it means that a lot of time and cpu cycles are wasted compiling non-fortran software that are unusable in the end. With this commit, the 'need_gfortarn' variable has been added 'reproduce/software/shell/configure.sh', in a new part that is devoted to project-specific features. If it equals '0', then the 'gfortran' test (and message!) isn't done at all, but if it is set to '1', then the configure stage will halt immediately gfortran is not found and not built. The default operations of the core Maneage branch don't need 'gfortran', so by default it is set to 0. But 'gfortran' is necessary for all projects that use Numpy (Python's numeric library) for example. So if your project needs 'gfortran', please set this new variable to 1. As mentioned in the comments of 'configure.sh', ideally we should detect this automatically, but we haven't had the time to implement it yet.
Diffstat (limited to 'reproduce/software/make')
0 files changed, 0 insertions, 0 deletions