(moving to petsc-dev, feel free to continue the “general” discussion on petsc-users)
> On 29 Jun 2020, at 10:03 PM, Pierre Jolivet <[email protected]> > wrote: > > Sorry for the noise, but maybe it’s better to put this in PETSc ./configure, > like you did here Satish > https://gitlab.com/petsc/petsc/-/commit/2cd8068296b34e127f055bb32f556e3599f17523 > > <https://gitlab.com/petsc/petsc/-/commit/2cd8068296b34e127f055bb32f556e3599f17523> > ? > If Gfortran100 && MS-MPI, then FFLAGS += "-fallow-invalid-boz" > WDY(PETSc-)GT? So, it looks like -fallow-invalid-boz is not as old as I thought… g++.exe (Rev1, Built by MSYS2 project) 9.3.0 Copyright (C) 2019 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Running Executable WITHOUT threads to time it out Executing: gfortran -c -o /tmp/petsc-kmp34jh9/config.setCompilers/conftest.o -I/tmp/petsc-kmp34jh9/config.setCompilers -fallow-invalid-boz /tmp/petsc-kmp34jh9/config.setCompilers/conftest.F90 Possible ERROR while running compiler: exit code 1 stderr: gfortran.exe: error: unrecognized command line option '-fallow-invalid-boz' Source: program main end Error testing Fortran compiler: Cannot compile FC with gfortran. Deleting "FC" Again, would it be OK if I add a check in MPI.py to force this option when isGfortran100plus and defined(HAVE_MSMPI)? Or do we expect Windows users to know about this ninja gfortran flag? Is this tested on some Cygwin box (MS-MPI 10.1.2 + gfortran 10)? I see arch-ci-mswin-intel.py is using MS-MPI (which version?) but with ifort. Thanks, Pierre
