<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">(moving to petsc-dev, feel free to continue the “general” discussion on petsc-users)<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 29 Jun 2020, at 10:03 PM, Pierre Jolivet <<a href="mailto:pierre.jolivet@enseeiht.fr" class="">pierre.jolivet@enseeiht.fr</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class=""><div class="">Sorry for the noise, but maybe it’s better to put this in PETSc ./configure, like you did here Satish <a href="https://gitlab.com/petsc/petsc/-/commit/2cd8068296b34e127f055bb32f556e3599f17523" class="">https://gitlab.com/petsc/petsc/-/commit/2cd8068296b34e127f055bb32f556e3599f17523</a> ?</div><div class="">If Gfortran100 && MS-MPI, then FFLAGS += "-fallow-invalid-boz"</div><div class="">WDY(PETSc-)GT?</div></div></div></div></blockquote><br class=""></div><div>So, it looks like -fallow-invalid-boz is not as old as I thought…</div><pre style="font-variant-ligatures: normal; orphans: 2; widows: 2;" class="">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.</pre><div class=""><pre style="font-variant-ligatures: normal; orphans: 2; widows: 2;" class="">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"</pre><div class="">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?</div></div><div class="">Is this tested on some Cygwin box (MS-MPI 10.1.2 + gfortran 10)?</div><div class="">I see arch-ci-mswin-intel.py is using MS-MPI (which version?) but with ifort.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Pierre</div></div></body></html>