Your message dated Mon, 05 Aug 2024 12:05:31 +0000
with message-id <[email protected]>
and subject line Bug#1075168: fixed in libgctp 2.0.0-7
has caused the Debian Bug report #1075168,
regarding libgctp: ftbfs with GCC-14
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 [email protected]
immediately.)
--
1075168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075168
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:libgctp
Version: 2.0.0-6
Severity: important
Tags: sid trixie
User: [email protected]
Usertags: ftbfs-gcc-14
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/libgctp_2.0.0-6_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html
[...]
| ~~~~~~~~~~~~~~~
inv_init.c:36:8: note: ‘azimuth’ was declared here
36 | double azimuth; /* azimuth
*/
| ^~~~~~~
inv_init.c:447:14: warning: ‘lon2’ may be used uninitialized
[-Wmaybe-uninitialized]
447 | *iflg = omerinvint(r_major,r_minor,scale_factor,azimuth,lon_origin,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
448 | lat_origin,false_easting,
false_northing,lon1,lat1,
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
449 | lon2,lat2,mode);
| ~~~~~~~~~~~~~~~
inv_init.c:41:8: note: ‘lon2’ was declared here
41 | double lon2; /* 2nd longitude point
*/
| ^~~~
inv_init.c:447:14: warning: ‘lat1’ may be used uninitialized
[-Wmaybe-uninitialized]
447 | *iflg = omerinvint(r_major,r_minor,scale_factor,azimuth,lon_origin,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
448 | lat_origin,false_easting,
false_northing,lon1,lat1,
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
449 | lon2,lat2,mode);
| ~~~~~~~~~~~~~~~
inv_init.c:43:8: note: ‘lat1’ was declared here
43 | double lat1; /* 1st standard parallel
*/
| ^~~~
inv_init.c:447:14: warning: ‘lat2’ may be used uninitialized
[-Wmaybe-uninitialized]
447 | *iflg = omerinvint(r_major,r_minor,scale_factor,azimuth,lon_origin,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
448 | lat_origin,false_easting,
false_northing,lon1,lat1,
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
449 | lon2,lat2,mode);
| ~~~~~~~~~~~~~~~
inv_init.c:44:8: note: ‘lat2’ was declared here
44 | double lat2; /* 2nd standard parallel
*/
| ^~~~
inv_init.c:447:14: warning: ‘lon_origin’ may be used uninitialized
[-Wmaybe-uninitialized]
447 | *iflg = omerinvint(r_major,r_minor,scale_factor,azimuth,lon_origin,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
448 | lat_origin,false_easting,
false_northing,lon1,lat1,
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
449 | lon2,lat2,mode);
| ~~~~~~~~~~~~~~~
inv_init.c:49:8: note: ‘lon_origin’ was declared here
49 | double lon_origin; /* longitude at origin
*/
| ^~~~~~~~~~
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c paksz.c -fPIC -DPIC -o .libs/paksz.o
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c lamccfor.c -o lamccfor.o >/dev/null 2>&1
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c untfz.c -fPIC -DPIC -o .libs/untfz.o
In file included from cproj.h:2,
from paksz.c:49:
proj.h:300:15: warning: ‘som_series’ declared ‘static’ but never defined
[-Wunused-function]
300 | static double som_series(double *fb, double *fa2, double *fa4, double
*fc1,
| ^~~~~~~~~~
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c lamccinv.c -o lamccinv.o >/dev/null 2>&1
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c for_init.c -o for_init.o >/dev/null 2>&1
In file included from untfz.c:26:
proj.h:300:15: warning: ‘som_series’ declared ‘static’ but never defined
[-Wunused-function]
300 | static double som_series(double *fb, double *fa2, double *fa4, double
*fc1,
| ^~~~~~~~~~
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c paksz.c -o paksz.o >/dev/null 2>&1
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c untfz.c -o untfz.o >/dev/null 2>&1
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c report.c -o report.o >/dev/null 2>&1
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall
-pedantic -fPIC -c inv_init.c -o inv_init.o >/dev/null 2>&1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/source'
make[2]: *** [Makefile:396: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:328: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:20: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: libgctp
Source-Version: 2.0.0-7
Done: Alastair McKinstry <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libgctp, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <[email protected]> (supplier of updated libgctp 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 05 Aug 2024 12:49:10 +0100
Source: libgctp
Architecture: source
Version: 2.0.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Alastair McKinstry <[email protected]>
Closes: 1075168
Changes:
libgctp (2.0.0-7) unstable; urgency=medium
.
* Use debhelper-compat (=13)
* Adapt d/rules to dh-compat 13 standard
* Set Debian Science Maint. as maintainer
* Fix broken vcs url
* Standards-Version: 4.7.0; no changes required
* Recommend pkgconf rather than pkg-config
* Patch g++14 tightens definitons for FTBFS with gcc 14. Closes: #1075168
Checksums-Sha1:
e7f1fa839c037817eef0db4350aa41d2d055f130 2024 libgctp_2.0.0-7.dsc
82a20219ad7a4429dd6b36c361e994462b6eb536 3624 libgctp_2.0.0-7.debian.tar.xz
Checksums-Sha256:
5ec55f2e9a94a89f3c5ca7a181dbbf31e1dc48d5d7cb5784c56037a8f75f595f 2024
libgctp_2.0.0-7.dsc
6fac77d3a5053b7ca43a7aa4b75264efe843c5c2996b49e1b747604b02d127f5 3624
libgctp_2.0.0-7.debian.tar.xz
Files:
e1f5be8bab14a02ef37d769c8810832f 2024 utils optional libgctp_2.0.0-7.dsc
2bbd1b64772cd004d008761a98dc4860 3624 utils optional
libgctp_2.0.0-7.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmawvIEACgkQy+a7Tl2a
06VA/BAAhSUT8K9eTjBMKMCmurx8bUQsl77dFavZ+7Nz4YIxuJkRzoQhf67OIZ1K
KkBlPAkwFP7qieUVvVGGD7dl6WPIqB0ejjukwXjRtJ8pyT7gLnu35BJKbdLxfl1a
ER7mSTSdgEn+h5qQMzzoTndI+Ony1ttPu95lmQvYPzptU+FnpGnpWJvlPF8e12ia
bE44e10ez8ipEEIPTjlg6zjx5aiCzP/xoBG2yBTN2d7JCwmiIvQT4SwPzuzl9Qik
7gsViM/mTHXypRnCCqDjUFWH+lrDp1ZLR6cX2zYwcXahN4QmDN8tH7iCXDfkJBUL
aozpKDSrXAySkx8UXYJjzAyAonaHCiOpqfViHpRZ5BbnQqTY7qBiEhK+qr+9q8cq
ovDjQBjjjboiOcJcYmW8Qp+chVJsKED+lfFx9gVC96MNZH8MJhvTxGplTSOJrq8I
o+anmcu82wSSGQ2cVEsTnExF7K8AJkVxs0ji66S3ZkQeta9bTXksEjJ3bGo2AdGU
15mv8urumR8TIKaU8CIKhrBJEWWYv8De97LLMzboGy7ZBu3tWqdSrzWh97IOzk8e
o2mn/S0K2hXC+hldw/jl2jN2jQSBX9JC9+Nb47Y+2D9CSf+WyxZcGGPchk8jvfXx
nyKe0uUoLf+CDqxyx5shCvWUcgB4FvC9ZRUa1knG+6paQawMiVI=
=kpOl
-----END PGP SIGNATURE-----
pgpzVvSNVzu3t.pgp
Description: PGP signature
--- End Message ---
