Your message dated Fri, 15 Nov 2019 22:50:42 +0000
with message-id <e1ivkqm-000cdw...@fasolo.debian.org>
and subject line Bug#944127: fixed in libcgns 3.4.0-1~exp2
has caused the Debian Bug report #944127,
regarding gfortran-9 causes libcgns FTBFS on ppc64el
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.)
--
944127: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944127
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gfortran-9
Severity: serious
Justification: Causes FTBFS
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
I've recently uploaded libcgns 8.4.0-1~exp1 to experimental. All builds but
ppc64el are ok.
The ppc64el failure [0] occurs in the test suite (test cgread_f03), when a C
va_arg function (src/cg_ftoc.c:cg_goto_f()) is called from Fortran code
(src/tests/cgread_f03.F90:421). This function is called several times. Is is
successful at first, then it fails badly because the corresponding hidden
string length parameters[1] are equal to 0. This shouldn't happen because the
related strings are literals: 'Zone_t', 'GridCoordinates_t', 'end'.
[0]
https://buildd.debian.org/status/fetch.php?pkg=libcgns&arch=ppc64el&ver=3.4.0-1%7Eexp1&stamp=1572269974&raw=0
[1] https://gcc.gnu.org/onlinedocs/gfortran/Argument-passing-conventions.html
Further investigation shows that release 3.3.0-6 of libcgns FTBFS the very same
way with GCC 8.3.0, while it succeeded with GCC 8.2.0 [2].
[2]
https://buildd.debian.org/status/fetch.php?pkg=libcgns&arch=ppc64el&ver=3.3.0-6%2Bb2&stamp=1542797186&raw=0
I then ran a bisect on the GCC svn branch 'gcc-8-branch' and found out that the
failure was introduced by the r269349 changeset [3].
[3] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=269349
This is a backport of the trunk r268992 changetset [4] introduced during GCC-9
development.
[4] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=268992
At this point I don't know where to go. I'm setting severity = serious because
this change now present into Debian/sid GCC-{7,8,9} makes libcgns FTBFS on
ppc64el. Feel free to downgrade it if you think it appropriate.
Any help appreciated. Many thanks in advance,
_g.
- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl3AXBgACgkQ7+hsbH/+
z4O20Af/U24cwYYZ52fdUfa82GGT8lMP2YIeZiOl9fm9F+6T1d5BFhJAUVGxei9e
3L+kGECJoTYcX8i3Ou0yKhPtuYCDaJ3ceBl93bBW5/obO+epWr3XLAkG5sVcJDO4
pHUh32dqjEuXCz6CZfPVv5bARSZpT9CUxyo1d6ylikfqbXCE0Rw8qeSj8Q2+iOyJ
xoLL9lZXLo9GnGvVz/O5+xtxulmF5F77uO+NmP6sr+7oqZydFb3j3f6//RTumpKs
Bco0A3tPtP71eCJsO+KwremHZV7MAAkUO5GBdQP7IcVj6rISJE08kI/hEmnP89wi
KcSoVYbi2Uax2lKqH/E57FqQlkkkHQ==
=5u/M
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Source: libcgns
Source-Version: 3.4.0-1~exp2
We believe that the bug you reported is fixed in the latest version of
libcgns, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gilles Filippini <p...@debian.org> (supplier of updated libcgns package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 15 Nov 2019 23:25:31 +0100
Source: libcgns
Architecture: source
Version: 3.4.0-1~exp2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Team
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Gilles Filippini <p...@debian.org>
Closes: 944127
Changes:
libcgns (3.4.0-1~exp2) experimental; urgency=medium
.
[ Jelmer Vernooij ]
* Change priority extra to priority optional.
.
[ Gilles Filippini ]
* New patch gcc-pr92361.patch to fix FTBFS on ppcel64 (closes: #944127)
Checksums-Sha1:
91988bcb4c8cacb0c434b060e52c127265edc8fd 1802 libcgns_3.4.0-1~exp2.dsc
26e0022df09705b589b9ea470ee59acc64946a51 12516
libcgns_3.4.0-1~exp2.debian.tar.xz
0c218419fef3f6755a62ae8d02cbe12f06328239 10097
libcgns_3.4.0-1~exp2_source.buildinfo
Checksums-Sha256:
671f2a7229aa995e643eaba104964b2b45ce57b7735cfb9ea53b63e8e9aa21b3 1802
libcgns_3.4.0-1~exp2.dsc
967075916ca7db86c81d658abdb57c4b65e1069a6d9bcff0e21638a949a08259 12516
libcgns_3.4.0-1~exp2.debian.tar.xz
91d074722caff365f8afe7c43c72211cfd3b69ad645343a9f974915d53f01c2c 10097
libcgns_3.4.0-1~exp2_source.buildinfo
Files:
3865bd0c673653db35110949c7fabcd6 1802 libs optional libcgns_3.4.0-1~exp2.dsc
683cc3c40b52b7f082fcb599140cfecf 12516 libs optional
libcgns_3.4.0-1~exp2.debian.tar.xz
5a050aae6bbeed392f50f09d99dc3f7d 10097 libs optional
libcgns_3.4.0-1~exp2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQFEBAEBCgAuFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl3PJnEQHHBpbmlAZGVi
aWFuLm9yZwAKCRDv6Gxsf/7Pg8gcB/4gW4QwK5Y6wtjtaCYWZLxrXvj2645LZGo6
KU8wGLOqYRIIsBEAr0QNfLALwz4WLhEq3cPPa6DYXqtnMy4cFteDCUjjXG1CRGQN
tZ8TRAKOJlsrHqexGgj7syr1HIo7yje5mRtXjmmzGjzlxusqeVd6F81GQ5jb0sL/
bGgq1Vi1jTkuYMWKZG7Jcg4k+XU5X+od26pntfsdvUzLDbU85LBuLmhSHKPTofXe
LfdOROBJc3d1MXD+2ubLoBXSEfi9RatB5x9U1fbd5Dpi2FxU46DEYk+of/yqz9i8
7UioJXLHR3WrGDQtYHQqUCWKtAUiH/76UbTvPbxwsuaOQjWZsKNr
=1qMk
-----END PGP SIGNATURE-----
--- End Message ---
