[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1098025: marked as done (ucspi-proxy: ftbfs with GCC-15)

Your message dated Fri, 10 Oct 2025 21:21:07 +0000
with message-id <E1v7KXz-006Cee-2u@fasolo.debian.org>
and subject line Bug#1098025: fixed in ucspi-proxy 0.99-8
has caused the Debian Bug report #1098025,
regarding ucspi-proxy: 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 owner@bugs.debian.org
immediately.)


-- 
1098025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098025
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:ucspi-proxy
Version: 0.99-7
Severity: important
Tags: sid forky
User: debian-gcc@lists.debian.org
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/ucspi-proxy_0.99-7_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

[...]
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
/usr/bin/make clean
make[1]: Entering directory '/build/reproducible-path/ucspi-proxy-0.99'
rm -f `cat TARGETS`
make[1]: Leaving directory '/build/reproducible-path/ucspi-proxy-0.99'
for i in `ls *'{orig}' || :`; do mv -vf $i ${i%'{orig}'}; done
ls: cannot access '*{orig}': No such file or directory
rm -f build-stamp configure-stamp
rm -rf '/build/reproducible-path/ucspi-proxy-0.99/debian/ucspi-proxy'
rm -f debian/files debian/substvars changelog
 debian/rules binary
for i in conf-*; do \
  test -e ${i%'{orig}'}'{orig}' || cp -v $i $i'{orig}'; \
done
'conf-bgincs' -> 'conf-bgincs{orig}'
'conf-bglibs' -> 'conf-bglibs{orig}'
'conf-bin' -> 'conf-bin{orig}'
'conf-cc' -> 'conf-cc{orig}'
'conf-ld' -> 'conf-ld{orig}'
'conf-man' -> 'conf-man{orig}'
echo '/usr/bin' >conf-bin
echo '/usr/include/bglibs' >conf-bgincs
echo 'gcc ${CPPFLAGS} ${CFLAGS}' >conf-cc
echo 'gcc ${LDFLAGS}' >conf-ld
echo '/usr/share/man' >conf-man
touch configure-stamp
/usr/bin/make CPPFLAGS="`dpkg-buildflags --get CPPFLAGS`" CFLAGS="`dpkg-buildflags --get CFLAGS`" LDFLAGS="`dpkg-buildflags --get LDFLAGS`"
make[1]: Entering directory '/build/reproducible-path/ucspi-proxy-0.99'
( echo '#!/bin/sh'; \
  echo 'lib="$1"; shift';\
  echo 'rm -f "$lib"';\
  echo 'ar cr "$lib" ${1+"$@"}';\
  echo 'ranlib "$lib"';\
) >makelib
chmod 755 makelib
( bgincs=`head -n 1 conf-bgincs`; \
  echo '#!/bin/sh'; \
  echo 'source=$1; shift'; \
  echo 'base=`echo "$source" | sed -e s:\\\\.c$::`'; \
  echo echo `head -n 1 conf-cc` -I. "-I'${bgincs}'" '-o ${base}.o -c $source ${1+"$@"}'; \
  echo exec `head -n 1 conf-cc` -I. "-I'${bgincs}'" '-o ${base}.o -c $source ${1+"$@"}'; \
) >compile
chmod 755 compile
./compile base64.c
gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ucspi-proxy-0.99=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -I. -I/usr/include/bglibs -o base64.o -c base64.c
In file included from /usr/include/bglibs/str.h:5,
                 from /usr/include/bglibs/base64.h:4,
                 from base64.c:4:
/usr/include/bglibs/sysdeps.h:91:12: error: conflicting types for ‘select’; have ‘int(void)’
   91 | extern int select();
      |            ^~~~~~
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:179,
                 from /usr/include/stdlib.h:514,
                 from base64.c:1:
/usr/include/x86_64-linux-gnu/sys/select.h:102:12: note: previous declaration of ‘select’ with type ‘int(int,  fd_set * restrict,  fd_set * restrict,  fd_set * restrict,  struct timeval * restrict)’
  102 | extern int select (int __nfds, fd_set *__restrict __readfds,
      |            ^~~~~~
In file included from base64.c:8:
ucspi-proxy.h:22:13: error: ‘bool’ cannot be defined via ‘typedef’
   22 | typedef int bool;
      |             ^~~~
ucspi-proxy.h:22:13: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
ucspi-proxy.h:22:1: warning: useless type name in empty declaration
   22 | typedef int bool;
      | ^~~~~~~
make[1]: *** [Makefile:15: base64.o] Error 1
make[1]: Leaving directory '/build/reproducible-path/ucspi-proxy-0.99'
make: *** [debian/rules:31: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: ucspi-proxy
Source-Version: 0.99-8
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
ucspi-proxy, 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 1098025@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated ucspi-proxy 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 10 Oct 2025 21:00:37 +0300
Source: ucspi-proxy
Architecture: source
Version: 0.99-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1098025
Changes:
 ucspi-proxy (0.99-8) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with GCC 15. (Closes: #1098025)
Checksums-Sha1:
 558ef7a292fc3b5f8fc9cc1e6c4ec170de7bc644 1837 ucspi-proxy_0.99-8.dsc
 db2efe111839a0b237e32f6da2f865ae1860e070 5732 ucspi-proxy_0.99-8.debian.tar.xz
Checksums-Sha256:
 4467f4c94b6104c5d371f56c54b44b47e79dd240c42ed4376aae635d64f8d8d7 1837 ucspi-proxy_0.99-8.dsc
 05ca03b51803bfbb2e2093b63590680d3905a96dc81c7d35612d9aae615b05de 5732 ucspi-proxy_0.99-8.debian.tar.xz
Files:
 fa14f3baa89e277fdd2201c66ff17dc9 1837 net optional ucspi-proxy_0.99-8.dsc
 62020a2afc3eb8908bc2491efbd95928 5732 net optional ucspi-proxy_0.99-8.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjpdOUACgkQiNJCh6LY
mLF/PA//bXPMqOe4W6VBQzVqZr3GQlcXDUYEnltXjQF4p8is4GTCLjkaoIkpvSGY
6NGW2nBb7uSO89aa2rEih0Fv1eyZXJ0Ka450xtWVZNjnLjjxefSY8/tywYTZJKyx
CcA514H78RInqtPGI8hn/OAFMEStMSacdxRzMOxvvjccQlg3/D0cB98ddmuTb4mV
7HckGypVwF5tVrxvTigCYqH01OY9++YToX+3ful1wuK2ETwqDVomPQ22beGwC/V3
8jEMCOakpgfJ5LUngLoUEsCH1tIXHVljm86JcWb/+IrqP+KC8KSG9e6N5Bw33s3o
oQUABfRINAGGxyMh5poDZ6DnNnRSwK94z+H5Ocm36a0sei3zrnChOMZk4uLJ77Kd
CpLwlAqcK20is0I27ELmpmIxNdE32sFlMl4NABIRetpxO+7QKRtz4ki2FaycN8pJ
CwaCEZ7ulcl9yKrT1jdUk3iDHq99PgbEASMFspK2H2mkDnLNESVs+YlVeOxeq+wQ
q/47Q4gHRWsij8pIE80kKkGcKOQeZExfgKdsEYpXZbA8mWrGHj+4QlrsSqULe0TR
xWGRp9IvLURLk2HHG8DD3vjWNIKgrBheq9eWDzLcoK+uwkQ7/v1sldknYlGdqQz8
tHLH1JAxNWQvXvGNhss3b9liltGrH8Z/HtQRK6GC9oiB87wmlR4=
=fcGU
-----END PGP SIGNATURE-----

Attachment: pgpn_Pv7w2bD4.pgp
Description: PGP signature


--- End Message ---
Reply to: