Your message dated Sun, 14 Sep 2025 04:54:29 +0000 with message-id <E1uxekv-005eu3-1i@fasolo.debian.org> and subject line Bug#1097911: fixed in soundmodem 0.20-8 has caused the Debian Bug report #1097911, regarding soundmodem: 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.) -- 1097911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097911 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: maintonly@bugs.debian.org
- Subject: soundmodem: ftbfs with GCC-15
- From: Matthias Klose <doko@debian.org>
- Date: Mon, 17 Feb 2025 17:54:22 +0000
- Message-id: <E1tk5K2-009QOT-IR@paradis.debian.org>
Package: src:soundmodem Version: 0.20-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/soundmodem_0.20-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 [...] | ^~~~~~~~~ meas.c: In function ‘main’: meas.c:438:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 438 | signal(SIGTERM, sigterm); | ^~~~~~~ | | | void (*)(void) In file included from /usr/include/x86_64-linux-gnu/sys/param.h:28, from meas.c:35: /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ meas.c:309:12: note: ‘sigterm’ declared here 309 | RETSIGTYPE sigterm() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ meas.c:439:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 439 | signal(SIGHUP, sigterm); | ^~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ meas.c:309:12: note: ‘sigterm’ declared here 309 | RETSIGTYPE sigterm() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ meas.c:440:24: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 440 | signal(SIGINT, sigterm); | ^~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ meas.c:309:12: note: ‘sigterm’ declared here 309 | RETSIGTYPE sigterm() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ meas.c:441:25: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types] 441 | signal(SIGQUIT, sigterm); | ^~~~~~~ | | | void (*)(void) /usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’ 88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler) | ~~~~~~~~~~~~~~~^~~~~~~~~ meas.c:309:12: note: ‘sigterm’ declared here 309 | RETSIGTYPE sigterm() | ^~~~~~~ /usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here 72 | typedef void (*__sighandler_t) (int); | ^~~~~~~~~~~~~~ make[3]: *** [Makefile:436: meas.o] Error 1 make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory '/build/reproducible-path/soundmodem-0.20/pammodem' make[2]: *** [Makefile:434: all-recursive] Error 1 make[2]: Leaving directory '/build/reproducible-path/soundmodem-0.20' make[1]: *** [Makefile:375: all] Error 2 make[1]: Leaving directory '/build/reproducible-path/soundmodem-0.20' dh_auto_build: error: make -j8 returned exit code 2 make: *** [debian/rules:13: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
- To: 1097911-close@bugs.debian.org
- Subject: Bug#1097911: fixed in soundmodem 0.20-8
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Sun, 14 Sep 2025 04:54:29 +0000
- Message-id: <E1uxekv-005eu3-1i@fasolo.debian.org>
- Reply-to: tony mancill <tmancill@debian.org>
Source: soundmodem Source-Version: 0.20-8 Done: tony mancill <tmancill@debian.org> We believe that the bug you reported is fixed in the latest version of soundmodem, 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 1097911@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill <tmancill@debian.org> (supplier of updated soundmodem 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: Sat, 13 Sep 2025 20:58:21 -0700 Source: soundmodem Architecture: source Version: 0.20-8 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org> Changed-By: tony mancill <tmancill@debian.org> Closes: 1097911 Changes: soundmodem (0.20-8) unstable; urgency=medium . * Team upload. * Add patch for FTBFS w/GCC-15 (Closes: #1097911) Checksums-Sha1: 04f79b1721e49f8337cbbab14c5094a5f0c9e495 2062 soundmodem_0.20-8.dsc b927f570f9c15c363cc5e7400adaf15ebc27d806 10272 soundmodem_0.20-8.debian.tar.xz c65339c0af7c1222aba0f290044bf22d81819866 12134 soundmodem_0.20-8_amd64.buildinfo Checksums-Sha256: a07b2cb895613cb2ad705f52e90e081f3a3175ac858008ea4728781edc3065df 2062 soundmodem_0.20-8.dsc 456c523851f92cc8ea501c08299e89512fa7002e73c41d98abce8d23e1bc1dff 10272 soundmodem_0.20-8.debian.tar.xz 2fa21817127219f6d48ad18c1610ec86d166836363401b674fc98bb27b3f2768 12134 soundmodem_0.20-8_amd64.buildinfo Files: cd047d8c113c6b414b8fabb8b8254347 2062 hamradio optional soundmodem_0.20-8.dsc 5c0831d4c52abd9c95b9b480273cfda5 10272 hamradio optional soundmodem_0.20-8.debian.tar.xz c7562b36a34ca84a5f94dbab6dc2832c 12134 hamradio optional soundmodem_0.20-8_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmjGRAcUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpazWw//dhq7Syv2ygCkXGK1c35NEk8Nozw2 iHdVm1C9aETbE3ZFCWp6VQ/U7HJjnJ61S86raa5Rc1cEXOoUS0mPQ1RnZpeHwFTK HKZ+7fTVusaalOAhdr1GR3UoAeuiOVv7GUPbNPCZDohlsr4wBcc3Q9DxOwFv0FCV QfkejJ43p0oOsFaDEQFt+BYUuJKn0lPcRumj010lpjC2T/hv3XlzhLGZD7vF7EH6 GttAsVoHV9tu1RgHgr1Bf7T/zADNFo4awlalkDZYJG5B8I0wR/PdIH+NJFDkrQps Vqpsa1tG3uwkQe3byEwhpfpbmYWcgCR9doouDS19CCiTlB7SDJzk3CUbAL7HI4JF t3Sw7ZWudLCQ73/7fyn1OYSktJPjXNnbV3mj/WqBH4AAudrfn7QZbHAfcBKVaIgl X3iHHr+nU3s6HGmQ8mU77KmoYtGDJcwUXc2XtyZ/1oCQSn8HdDPIjPti2HvkKId4 51pkCtSvJ8AnoxHlEyLvbP7kwqbh3koUhmfGbRMAbdu5EzPNLas2ix6HjQcCe0N5 2eFB+HBYVuEbBVlnmfKQ6dTRLQJlJfF6sUpsqlg+kO7/vOOWWEk7piqmhEXI5Cuh YF7oxx+yR50OH2JfuMg1LfipxzzpRvGLk6F9yclu4JGifnlUg6DLqDf8/+quiRoX zlgf81/tI+jHy1I= =RnMH -----END PGP SIGNATURE-----Attachment: pgp7Ngo9mHITN.pgp
Description: PGP signature
--- End Message ---