Your message dated Tue, 09 Sep 2025 15:08:11 +0000
with message-id <[email protected]>
and subject line Bug#1097576: fixed in pgpool2 4.6.3-2
has caused the Debian Bug report #1097576,
regarding pgpool2: ftbfs with GCC-15
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.)
--
1097576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:pgpool2
Version: 4.5.5-1
Severity: important
Tags: sid forky
User: [email protected]
Usertags: ftbfs-gcc-15
[This bug is NOT 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-15/g++-15, but succeeds to build with gcc-14/g++-14. The
severity of this report will be raised before the forky release.
The full build log can be found at:
http://qa-logs.debian.net/2025/02/16/amd64exp/pgpool2_4.5.5-1_unstable_gccexp.log.gz
The last lines of the build log are at the end of this report.
To build with GCC 15, either set CC=gcc-15 CXX=g++-15 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
GCC 15 now defaults to the C23/C++23 standards, exposing many FTBFS.
Other 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-15/porting_to.html
[...]
checking for openssl/ssl.h... yes
checking for CRYPTO_new_ex_data in -lcrypto... yes
checking for SSL_new in -lssl... yes
checking for ldap_bind in -lldap... yes
checking for ldap.h... yes
checking for ldap_initialize... yes
checking for pam_start in -lpam... yes
checking for security/pam_appl.h... yes
checking for libmemcached/memcached.h... yes
checking for memcached_create in -lmemcached... yes
checking for PQexecPrepared in -lpq... yes
checking for PQprepare... yes
checking for PQpingParams... yes
checking whether to use row lock against the sequence table for insert_lock...
no
checking whether to use table lock against the target table for insert_lock...
no
enable cassert = no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating doc/src/Makefile
config.status: creating doc/src/sgml/Makefile
config.status: creating doc.ja/Makefile
config.status: creating doc.ja/src/Makefile
config.status: creating doc.ja/src/sgml/Makefile
config.status: creating src/Makefile
config.status: creating src/include/Makefile
config.status: creating src/parser/Makefile
config.status: creating src/libs/Makefile
config.status: creating src/libs/pcp/Makefile
config.status: creating src/tools/Makefile
config.status: creating src/tools/pgmd5/Makefile
config.status: creating src/tools/pgenc/Makefile
config.status: creating src/tools/pcp/Makefile
config.status: creating src/tools/pgproto/Makefile
config.status: creating src/tools/watchdog/Makefile
config.status: creating src/watchdog/Makefile
config.status: creating src/include/config.h
config.status: executing libtool commands
# create directory here so we can unlink it in case autopkgtest leaves files
owned by root behind
mkdir -p src/test/jdbc/result
make[1]: Leaving directory '/build/reproducible-path/pgpool2-4.5.5'
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/reproducible-path/pgpool2-4.5.5'
/usr/bin/make
make[2]: Entering directory '/build/reproducible-path/pgpool2-4.5.5'
Making all in src
make[3]: Entering directory '/build/reproducible-path/pgpool2-4.5.5/src'
Making all in parser
make[4]: Entering directory '/build/reproducible-path/pgpool2-4.5.5/src/parser'
gcc -DHAVE_CONFIG_H -I. -I../../src/include -D_GNU_SOURCE -I
../../src/include/parser -I /usr/include/postgresql -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/build/reproducible-path/pgpool2-4.5.5=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection -Wall -Wmissing-prototypes
-Wmissing-declarations -Wno-format-truncation -Wno-stringop-truncation
-fno-strict-aliasing -c -o copyfuncs.o copyfuncs.c
In file included from ../../src/include/pool.h:28,
from copyfuncs.c:24:
../../src/include/pool_type.h:44:14: error: ‘bool’ cannot be defined via
‘typedef’
44 | typedef char bool;
| ^~~~
../../src/include/pool_type.h:44:14: note: ‘bool’ is a keyword with ‘-std=c23’
onwards
../../src/include/pool_type.h:44:1: warning: useless type name in empty
declaration
44 | typedef char bool;
| ^~~~~~~
make[4]: *** [Makefile:439: copyfuncs.o] Error 1
make[4]: Leaving directory '/build/reproducible-path/pgpool2-4.5.5/src/parser'
make[3]: *** [Makefile:941: all-recursive] Error 1
make[3]: Leaving directory '/build/reproducible-path/pgpool2-4.5.5/src'
make[2]: *** [Makefile:421: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/pgpool2-4.5.5'
make[1]: *** [debian/rules:35: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/reproducible-path/pgpool2-4.5.5'
make: *** [debian/rules:70: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: pgpool2
Source-Version: 4.6.3-2
Done: Christoph Berg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
pgpool2, 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.
Christoph Berg <[email protected]> (supplier of updated pgpool2 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: SHA512
Format: 1.8
Date: Tue, 09 Sep 2025 15:15:13 +0200
Source: pgpool2
Architecture: source
Version: 4.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <[email protected]>
Changed-By: Christoph Berg <[email protected]>
Closes: 1097576
Changes:
pgpool2 (4.6.3-2) unstable; urgency=medium
.
* Fix FTBFS with gcc-15. (Closes: #1097576)
* debian/pgversions: Bump to 11+.
Checksums-Sha1:
3f5c68ea7d557085e10bc3624f213d80c5c593e4 2694 pgpool2_4.6.3-2.dsc
c519a48faef8318ab0795656b8cfc03497478019 21388 pgpool2_4.6.3-2.debian.tar.xz
Checksums-Sha256:
48e7955a0baab6dc475465696cb97514a4f3630b8987d683dd73baf77fc1d8e3 2694
pgpool2_4.6.3-2.dsc
dfd49792eda6b2d079ee1e615ed16d32ad52da687754333742a5d3755df6f7d1 21388
pgpool2_4.6.3-2.debian.tar.xz
Files:
ab226f1492aca55c69e64949a90244da 2694 database optional pgpool2_4.6.3-2.dsc
55c0d207bd4241805529f04495901680 21388 database optional
pgpool2_4.6.3-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmjAOlMACgkQTFprqxLS
p64j0w/9FToUtQxzOvxT4An+r9N1njFvgCq4T7Ks2HTMTveMJ/ycS6J3rcqQEfqD
w7FSHH+ehMmRw9+xgRKnV469DNYN3BbE6o7lxz3uc5yE54XlMnqNe5vaOHjJIbdb
axON9GYUd22cofdLqylI5M2P1hEWIJVKwl5M1+Gf1VNXU6yRWKgqN2nTgQante0P
WtkR613YaukWD6fEbKGpOtg3cAu/eBMi1TuH8eq9MJbc8sFg5awQ8yiWpoKgrPk1
SdZ5XCbfuxSmW2L2kVYCoe/c3zow55UyFDzTc1AVAZn5nOD7W/54k+bveHqK4d7y
vCQeMkCqtF5JdDYse3emqYbtL0dNmwSZtu1f81+vLtSMgHkHjBYHf/v7kM7v8kXC
v6MZg3RGbJKA5+IKprChepKysULIqLnzOa/uvYHMPzIjWqVaPBjae4YSotaebZWw
gYFwwr0wVkMh21f8UqLFS+GEnVgQ+6TVDk+xfhpNRZPi35/s58XVORSHYrFO5JE2
StgOvIIjVqVOYJ0xIjPoPRiZRg2iF79ymn1QlF0CkGnYDhsaUGdJazkSqhQMZYud
hihEqooUOw5HASyCde5jbnbLO4PTVOLeiA6goBDOIpH127DhXP88+pyMhY71AC3D
PKRXZIQrmW4/zv6BVjDp5uySi3RYadtrqyQz4S+yXsOH51OiWYY=
=V0gM
-----END PGP SIGNATURE-----
pgpVUJQ2ZtVSH.pgp
Description: PGP signature
--- End Message ---
