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

Bug#1096477: marked as done (crashme: ftbfs with GCC-15)

Your message dated Tue, 23 Sep 2025 13:04:47 +0000
with message-id <E1v12hL-001rD0-16@fasolo.debian.org>
and subject line Bug#1096477: fixed in crashme 2.8.5-4
has caused the Debian Bug report #1096477,
regarding crashme: 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.)


-- 
1096477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096477
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:crashme
Version: 2.8.5-2
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/crashme_2.8.5-2_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

[...]
      |                       void (*)(int)
crashme.c:412:28: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’
  412 | my_signal (int sig, void (*func) ())
      |                     ~~~~~~~^~~~~~~~
crashme.c:361:1: note: ‘again_handler’ declared here
  361 | again_handler (int sig)
      | ^~~~~~~~~~~~~
crashme.c:441:22: error: passing argument 2 of ‘my_signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  441 |   my_signal (SIGIOT, again_handler);
      |                      ^~~~~~~~~~~~~
      |                      |
      |                      void (*)(int)
crashme.c:412:28: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’
  412 | my_signal (int sig, void (*func) ())
      |                     ~~~~~~~^~~~~~~~
crashme.c:361:1: note: ‘again_handler’ declared here
  361 | again_handler (int sig)
      | ^~~~~~~~~~~~~
crashme.c:447:23: error: passing argument 2 of ‘my_signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  447 |   my_signal (SIGALRM, again_handler);
      |                       ^~~~~~~~~~~~~
      |                       |
      |                       void (*)(int)
crashme.c:412:28: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’
  412 | my_signal (int sig, void (*func) ())
      |                     ~~~~~~~^~~~~~~~
crashme.c:361:1: note: ‘again_handler’ declared here
  361 | again_handler (int sig)
      | ^~~~~~~~~~~~~
crashme.c:449:22: error: passing argument 2 of ‘my_signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  449 |   my_signal (SIGINT, again_handler);
      |                      ^~~~~~~~~~~~~
      |                      |
      |                      void (*)(int)
crashme.c:412:28: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’
  412 | my_signal (int sig, void (*func) ())
      |                     ~~~~~~~^~~~~~~~
crashme.c:361:1: note: ‘again_handler’ declared here
  361 | again_handler (int sig)
      | ^~~~~~~~~~~~~
crashme.c: In function ‘monitor_fcn’:
crashme.c:959:23: error: passing argument 2 of ‘my_signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  959 |   my_signal (SIGALRM, monitor_fcn);
      |                       ^~~~~~~~~~~
      |                       |
      |                       void (*)(int)
crashme.c:412:28: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’
  412 | my_signal (int sig, void (*func) ())
      |                     ~~~~~~~^~~~~~~~
crashme.c:956:1: note: ‘monitor_fcn’ declared here
  956 | monitor_fcn (int sig)
      | ^~~~~~~~~~~
crashme.c: In function ‘vfork_main’:
crashme.c:1009:27: error: passing argument 2 of ‘my_signal’ from incompatible pointer type [-Wincompatible-pointer-types]
 1009 |       my_signal (SIGALRM, monitor_fcn);
      |                           ^~~~~~~~~~~
      |                           |
      |                           void (*)(int)
crashme.c:412:28: note: expected ‘void (*)(void)’ but argument is of type ‘void (*)(int)’
  412 | my_signal (int sig, void (*func) ())
      |                     ~~~~~~~^~~~~~~~
crashme.c:956:1: note: ‘monitor_fcn’ declared here
  956 | monitor_fcn (int sig)
      | ^~~~~~~~~~~
make[1]: *** [makefile:15: crashme.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/build/reproducible-path/crashme-2.8.5'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: crashme
Source-Version: 2.8.5-4
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
crashme, 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 1096477@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 crashme 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: Tue, 23 Sep 2025 15:43:29 +0300
Source: crashme
Architecture: source
Version: 2.8.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1096477
Changes:
 crashme (2.8.5-4) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with GCC 15. (Closes: #1096477)
Checksums-Sha1:
 6e4c8bd163668fd9232ba7d5d65f0db93a58249e 1852 crashme_2.8.5-4.dsc
 beb2339c2cc6dce385fa75049dff002d4447a2b2 6336 crashme_2.8.5-4.debian.tar.xz
Checksums-Sha256:
 7ec6a0d1154aa9615a7b0fb16ba614a227f92895c80d37e9e4aa4fc0487920ec 1852 crashme_2.8.5-4.dsc
 6136221829524053b3f4a93de8dbfc8079d52f92bdcf3bdf7dc05a5647b76a5e 6336 crashme_2.8.5-4.debian.tar.xz
Files:
 c0fc22510cd1d5cbccc9c23861f5f355 1852 devel optional crashme_2.8.5-4.dsc
 475c6f8ee0222684c1925e75fb396fe2 6336 devel optional crashme_2.8.5-4.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjSlkIACgkQiNJCh6LY
mLHAhw/+JNXG1soatY3oPBd14HJ+TPnBzAVRUsP4MnetaFAVTCI1ZzGv95vRwO+G
hn0dkIDMJgsmSzgL97Rfb8P3chgeiafDNrjvPCRxTfztphB+wKEgu4IxEOLNKq2n
2jU2DeE1q7zh2h31cWe2iQkxBMFekj8Y8AT5oqAXGHhTSg+FxoXDY0888gMnX7RQ
2IOvTtJ4CDqV+4l9XoTd8vwO7ukjvpu8kzdYFnHaJ2Fm3kuPAUeROg6sIOyUcbYs
QHn3a6fDTGVylfb+smVZjob6vKF94s76LYaupxSzJJPCtNnDuR/4wqWyX/I9sgfU
rRRQjv6jpoKo4J5GWRYBKuDrlwIqcFmw0AuoaL4hWr9iLC8MoOipXvgv0NwaTWEy
1id63bXPTIc7PcM00s9lgXbjpadVE/CANiMdJXdd3ELnPSNyKEmmlSOVJbK4DgLR
RFSMokwLMjpTu7jFEqVxNQss+u2zNeBDUAxV2yq7WG4CBwidtzreeY1AHfjsGSIh
8sENH/Sq//wwu+zWBQGbIM59ONhE+gO/ETjiSJlIRWV7TGBzQAdSAuMY5Frxivx+
YEy/EEpwd1HdPE0s24F5ML97kjzPuXl+9sq5PGFNEletTPaOhLQqzjllE8KhtWH7
e7C8uQO9jEs+iWHEwKyObFs9ipVPg/Pcnsztd+7C2N2cvv3k+7E=
=UmxY
-----END PGP SIGNATURE-----

Attachment: pgpsil0G6E5jg.pgp
Description: PGP signature


--- End Message ---
Reply to: