Your message dated Tue, 24 Dec 2024 01:08:47 +0100
with message-id <223ffbe0-148f-1362-ff55-6ff05d24e...@debian.org>
and subject line Re: libmpich-dev: mpicc adds compiler specific flags and fails
for older gcc versions
has caused the Debian Bug report #791676,
regarding libmpich-dev: mpicc adds compiler specific flags and fails for older
gcc versions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
791676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpich-dev
Version: 3.1-5+b2
Severity: normal
Dear Maintainer,
the mpicc.mpich allows to exchange the underlying compiler via the "-cc="
parameter.
Calling
> mpicc.mpich -cc=gcc-4.8 test.c
fails, as gcc will complain about unknown compiler flags.
I'd expect that passing different compiler via -cc=... results working mpi
program.
%%%%%%%%%%
Let's look at this in a bit more details...
The problem underneath becomes obvious when asking for the compiler flags:
> mpicc.mpich -compile_info
gcc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror
=format-security -Wl,-z,relro -I/usr/include/mpich -L/usr/lib/x86_64-linux-gnu
-lmpich -lopa -lmpl -lrt -lcr -lpthread
the output contains the "-fstack-protector-strong" parameter, which is not
available with gcc-4.8
alternatively you can ask via pkg-config
> pkg-config --cflags mpich
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat -Werror=format-
security -I/usr/include/mpich
The problem is here that the actual compiler flags and the compiler are mixed.
When switching to use "-fstack-protector-strong" Debian basically decided to
use a different compiler, so in my opinion the right configuration is (in make-
style):
CC="gcc -fstack-protector-strong"
CFLAGS="-D_FORTIFY_SOURCE=2 -g -O2 -Wformat -Werror=format-security
-I/usr/include/mpich"
When the "-fstack-protector-strong" parameter is part of the compiler command,
the compiler can be exchanged without problems.
-- System Information:
Debian Release: stretch/sid
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'oldoldstable'), (500,
'testing'), (400, 'stable'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libmpich-dev depends on:
ii g++ 4:4.9.2-4
ii gfortran 4:4.9.2-4
ii libc6 2.19-18
ii libcr-dev 0.8.5-2.2
ii libcr0 0.8.5-2.2
ii libmpich12 3.1-5+b2
ii libmpl-dev 3.1-5+b2
ii libopa-dev 3.1-5+b2
Versions of packages libmpich-dev recommends:
ii mpich 3.1-5+b2
libmpich-dev suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.0~b1-1
On Mon, 16 Nov 2020 17:47:51 +0800 Drew Parsons <dpars...@debian.org> wrote:
Package: libmpich-dev
Version: 3.4~a2+really3.3.2-2
$ MPICH_FC=gfortran-9 mpifort.mpich a.f90
gfortran-9: error: unrecognized command line option ‘-fallow-invalid-boz’
gfortran-9: error: unrecognized command line option
‘-fallow-argument-mismatch’; did you mean ‘-Wno-argument-mismatch’?
This should have been fixed a few years ago already ...
Andreas
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
