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

Bug#1096848: marked as done (ipsvd: ftbfs with GCC-15)

Your message dated Wed, 26 Feb 2025 11:41:55 +0000
with message-id <E1tnFnX-00CkYy-RX@fasolo.debian.org>
and subject line Bug#1096848: fixed in ipsvd 1.0.0-12
has caused the Debian Bug report #1096848,
regarding ipsvd: 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.)


-- 
1096848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096848
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:ipsvd
Version: 1.0.0-11
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/ipsvd_1.0.0-11_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

[...]
./choose cl trysgact hassgact.h1 hassgact.h2 >hassgact.h
./choose cl trysgprm hassgprm.h1 hassgprm.h2 >hassgprm.h
./compile chkshsgr.c
+ exec gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ipsvd-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -c chkshsgr.c
./load chkshsgr
+ exec gcc -Wl,-z,relro -o chkshsgr chkshsgr.o
./chkshsgr || (cat warn-shsgr; exit 1)
./choose clr tryshsgr hasshsgr.h1 hasshsgr.h2 >hasshsgr.h
./choose cl trywaitp haswaitp.h1 haswaitp.h2 >haswaitp.h
./choose clr trypoll iopause.h1 iopause.h2 >iopause.h
./choose c trysysel select.h1 select.h2 >select.h
./choose clr tryulong64 uint64.h1 uint64.h2 >uint64.h
( (./compile tryulong32.c && ./load tryulong32 && \
./tryulong32) >/dev/null 2>&1 \
&& cat uint32.h2 || cat uint32.h1) >uint32.h
rm -f tryulong32.o tryulong32
./compile trysocketlib.c
+ exec gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ipsvd-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -c trysocketlib.c
(./load trysocketlib >/dev/null 2>&1 || \
  (./load trysocketlib -lxnet >/dev/null 2>&1 && echo '-lxnet') || \
  (./load trysocketlib -lsocket -lnsl >/dev/null 2>&1 && \
    echo '-lsocket -lnsl') ) >socket.lib
rm -f trysocketlib.o trysocketlib
rm -f sysdeps
cat systype compile load socket.lib >>sysdeps
grep sysdep direntry.h >>sysdeps
grep sysdep haswaitp.h >>sysdeps
grep sysdep hassgact.h >>sysdeps
grep sysdep hassgprm.h >>sysdeps
grep sysdep select.h >>sysdeps
grep sysdep uint64.h >>sysdeps
grep sysdep iopause.h >>sysdeps
grep sysdep hasmkffo.h >>sysdeps
grep sysdep hasflock.h >>sysdeps
grep sysdep hasshsgr.h >>sysdeps
cat sysdeps
linux-6.1.0-28-cloud-amd64-:-:-:x86_64-:-
#!/bin/sh
# WARNING: This file was auto-generated. Do not edit!
set -x
exec gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ipsvd-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -c ${1+"$@"}
#!/bin/sh
# WARNING: This file was auto-generated. Do not edit!
main="$1"; shift
set -x
exec gcc -Wl,-z,relro -o "$main" "$main".o ${1+"$@"}
/* sysdep: +dirent */
/* sysdep: +waitpid */
/* sysdep: +sigaction */
/* sysdep: +sigprocmask */
/* sysdep: +sysselect */
/* sysdep: -ulong64 */
/* sysdep: -poll */
/* sysdep: +mkfifo */
/* sysdep: +flock */
/* sysdep: -shortsetgroups */
./compile tcpsvd.c
+ exec gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/ipsvd-1.0.0=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -c tcpsvd.c
tcpsvd.c: In function ‘sig_child_handler’:
tcpsvd.c:140:14: error: too many arguments to function ‘wait_nohang’; expected 0, have 1
  140 |   while ((i =wait_nohang(&wstat)) > 0) {
      |              ^~~~~~~~~~~ ~~~~~~
In file included from tcpsvd.c:25:
wait.h:7:12: note: declared here
    7 | extern int wait_nohang();
      |            ^~~~~~~~~~~
make[1]: *** [Makefile:65: tcpsvd.o] Error 1
make[1]: Leaving directory '/build/reproducible-path/ipsvd-1.0.0/ipsvd-1.0.0/compile'
make: *** [debian/rules:28: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: ipsvd
Source-Version: 1.0.0-12
Done: Andreas Beckmann <anbe@debian.org>

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

Debian distribution maintenance software
pp.
Andreas Beckmann <anbe@debian.org> (supplier of updated ipsvd 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: SHA256

Format: 1.8
Date: Wed, 26 Feb 2025 12:15:24 +0100
Source: ipsvd
Architecture: source
Version: 1.0.0-12
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Beckmann <anbe@debian.org>
Closes: 1096848 1098859
Changes:
 ipsvd (1.0.0-12) unstable; urgency=medium
 .
   * QA upload.
   * Revert fakeroot workarounds, sbuild has been fixed.  (Closes: #1098859)
   * Fix FTBFS with GCC-15.  (Closes: #1096848)
Checksums-Sha1:
 0d6a3b8e6f789b65fc8a57c0ae65e90912f8e3f9 1775 ipsvd_1.0.0-12.dsc
 19e302a4b0b7146c33e73154a40e404bdc812fd6 9116 ipsvd_1.0.0-12.debian.tar.xz
 4dda9797c89ddca9f9e4047e4bfed9953bb8b6a7 4459 ipsvd_1.0.0-12_source.buildinfo
Checksums-Sha256:
 a1fc860942ebcc306e2c7fd9fafb9b020de6b11a8a3b44576909cdfd79b74bf7 1775 ipsvd_1.0.0-12.dsc
 375c8b711ca99e4fd1f582748e2a1a9d87d135d30ea6029d603827e1b8a0c3ed 9116 ipsvd_1.0.0-12.debian.tar.xz
 04bd39391a301bf699ddd12ac4d3cbaa47b5c70dc503dc32d6df0f4edf907565 4459 ipsvd_1.0.0-12_source.buildinfo
Files:
 7f21e13e400ee2a3c0676c5f7516e86c 1775 net optional ipsvd_1.0.0-12.dsc
 72104018352c5060c1c39eb7661e4b72 9116 net optional ipsvd_1.0.0-12.debian.tar.xz
 0a4848a4370aff29b7a4502fda91bb41 4459 net optional ipsvd_1.0.0-12_source.buildinfo

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

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAme++CgQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCOXvD/9s9ETVfVyL/GKG16sNqNYb+5hDABbsnmGt
f2RA8d+eJeff6v0Eg6gLx5mqjKzSflMkmPsmGZUfSJdxffKpVVL+ZiNqbGnxd3Lx
2Y5e6B1Kgq92iGMzXCYdrtbPbyMhhO3VFoLHcaNCVo4P4nJJPf22W0p90N1vhe2d
6ecXMPdi/CgQKdyCB8sqYm+da1IS6a8TPQ5aaXTBtrLavTRnmcRLJK1CwjPAqF1W
oHpKyDkRNkT6+DKNkBz99KxmcMxQTJJ0u14Eao+vNuBS8gtuFtZhssnzYSbMKqaf
bPVIxTs4WGfCzE1zegn29/tIDypTVZELQSMSQUmqYkD4NFVdthwfEy00Zw3xvRnj
MDkxP8onOuGMOP8N74A6S7cwcO4gzr23CdZ7MvMY9qpmW/STeqay+9MGVphn3BDL
n/jB4UVYsGrx6mCrFVlitXymwD1XjUdDuMx5nVhyQ7kGNcWqyV9h1cw3WotaEDXm
jBmtqnxLIo1hndOjQDN7xQ0n7NlpJJ+2wmglI35lsWDKKXLGw9Et4qCGHceUMMI6
MTXh0LossYTUE9/U6GKdrKdqta98DA8LQFVHoQJeLu7qk/b9hJeMV4aHFoNH0+Y7
DZwbSkAND5ac1K+seXiNR7wiN1WlyWvmt48DuJCHKzrm8kTbBnaIqKv7ZLAbQWqd
sSDUdUXebA==
=36IW
-----END PGP SIGNATURE-----

Attachment: pgpAB_pdEsp67.pgp
Description: PGP signature


--- End Message ---
Reply to: