Re: Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags
This looks like it should be fixed by requiring gfortran >= 10 on the libmpich-dev control, yes? Sorry I'm slow in responding - on holiday Alastair On 11/08/2020 02:46, Drew Parsons wrote: Thanks Jed. I think you're replying here in response to discussion raised elsewhere. Could you provide a url link if its publicly accessible so we can catch the rest of the context? Drew On 2020-08-11 06:43, Jed Brown wrote: I'm replying here because I think it's part of this bug, but more severe in practice. It was evidently built with gfortran-10, but depends on gfortran-9, which doesn't recognize these arguments. $ cat > a.f90 program main end ^D $ mpifort a.f90 f95: error: unrecognized command line option ‘-fallow-invalid-boz’ f95: error: unrecognized command line option ‘-fallow-argument-mismatch’; did you mean ‘-Wno-argument-mismatch’? This can be worked around if one has gfortran-10 installed: $ MPICH_CC=gfortran-10 mpifort a.f90 $ $ mpifort -show f95 -O2 -fdebug-prefix-map=/build/mpich-Aiaw9P/mpich-3.4~a2+really3.3.2=. -fstack-protector-strong -fallow-invalid-boz -fallow-argument-mismatch -Wl,-z,relro -I/usr/include/x86_64-linux-gnu/mpich -I/usr/include/x86_64-linux-gnu/mpich -L/usr/lib/x86_64-linux-gnu -lmpichfort -lmpich -- Alastair McKinstry, email: alast...@sceal.ie, matrix: @alastair:sceal.ie, phone: 087-6847928 Green Party Councillor, Galway County Council -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags
On 2020-08-11 09:46, Drew Parsons wrote: Thanks Jed. I think you're replying here in response to discussion raised elsewhere. Could you provide a url link if its publicly accessible so we can catch the rest of the context? Oh wait, I'm wrong aren't I? Your reply is to Christian Engwer's question in Debian Bug#791676 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791676) The glitch with mpifort a.f90 and gfortran-10/gfortran-9 might be a temporary problem. We're still in the transition from gcc-9 to gcc-10. "mpifort a.f90" succeeds in debian unstable. The problem here is that the gfortran package is 1.185.1 (defaulting to gcc-9) in debian testing, but 1.188 (gcc-10) in debian unstable. The transition is held up by seqan, which is failing tests (see https://tracker.debian.org/pkg/gcc-defaults) Since our default MPI is OpenMPI, we didn't catch the inconsistency in mpich soon enough. mpich 3.4~a2+really3.3.2-2 was recently built against gcc-10, but its gfortran dependency was not strict and so it migrated into debian testing ahead of gfortran (with the gfortran-10 default). Drew -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags
Thanks Jed. I think you're replying here in response to discussion raised elsewhere. Could you provide a url link if its publicly accessible so we can catch the rest of the context? Drew On 2020-08-11 06:43, Jed Brown wrote: I'm replying here because I think it's part of this bug, but more severe in practice. It was evidently built with gfortran-10, but depends on gfortran-9, which doesn't recognize these arguments. $ cat > a.f90 program main end ^D $ mpifort a.f90 f95: error: unrecognized command line option ‘-fallow-invalid-boz’ f95: error: unrecognized command line option ‘-fallow-argument-mismatch’; did you mean ‘-Wno-argument-mismatch’? This can be worked around if one has gfortran-10 installed: $ MPICH_CC=gfortran-10 mpifort a.f90 $ $ mpifort -show f95 -O2 -fdebug-prefix-map=/build/mpich-Aiaw9P/mpich-3.4~a2+really3.3.2=. -fstack-protector-strong -fallow-invalid-boz -fallow-argument-mismatch -Wl,-z,relro -I/usr/include/x86_64-linux-gnu/mpich -I/usr/include/x86_64-linux-gnu/mpich -L/usr/lib/x86_64-linux-gnu -lmpichfort -lmpich -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#791676: libmpich-dev 3.4~a2+really3.3.2-2 has broken Fortran due to gfortran-10 specific flags
I'm replying here because I think it's part of this bug, but more severe in practice. It was evidently built with gfortran-10, but depends on gfortran-9, which doesn't recognize these arguments. $ cat > a.f90 program main end ^D $ mpifort a.f90 f95: error: unrecognized command line option ‘-fallow-invalid-boz’ f95: error: unrecognized command line option ‘-fallow-argument-mismatch’; did you mean ‘-Wno-argument-mismatch’? This can be worked around if one has gfortran-10 installed: $ MPICH_CC=gfortran-10 mpifort a.f90 $ $ mpifort -show f95 -O2 -fdebug-prefix-map=/build/mpich-Aiaw9P/mpich-3.4~a2+really3.3.2=. -fstack-protector-strong -fallow-invalid-boz -fallow-argument-mismatch -Wl,-z,relro -I/usr/include/x86_64-linux-gnu/mpich -I/usr/include/x86_64-linux-gnu/mpich -L/usr/lib/x86_64-linux-gnu -lmpichfort -lmpich -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
