Debian Bug report logs - #1096478
crasm: ftbfs with GCC-15

Reply or subscribe to this bug.

Display info messages

Message #5 received at maintonly@bugs.debian.org (full text, mbox, reply):

From: Matthias Klose <doko@debian.org>

To: maintonly@bugs.debian.org

Subject: crasm: ftbfs with GCC-15

Date: Mon, 17 Feb 2025 17:08:30 +0000

Package: src:crasm
Version: 1.8-3
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/crasm_1.8-3_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

[...]
      |             ^~~~~~~
parse.c:97:66: error: initialization of ‘void (*)(void)’ from incompatible pointer type ‘void (*)(struct result *, char *)’ [-Wincompatible-pointer-types]
   97 |         { "%?"          ,-2,1   /* binaire      */              ,cstbinary,},
      |                                                                  ^~~~~~~~~
parse.c:97:66: note: (near initialization for ‘oplist[20].callop’)
parse.c:60:13: note: ‘cstbinary’ declared here
   60 | extern void cstbinary(struct result *presult, char *s);
      |             ^~~~~~~~~
parse.c:98:66: error: initialization of ‘void (*)(void)’ from incompatible pointer type ‘void (*)(struct result *, char *)’ [-Wincompatible-pointer-types]
   98 |         { "?B"          ,-2,1   /* Intel binaire*/              ,cstbinary,},
      |                                                                  ^~~~~~~~~
parse.c:98:66: note: (near initialization for ‘oplist[21].callop’)
pseudos.c: In function ‘Xcpu’:
parse.c:60:13: note: ‘cstbinary’ declared here
   60 | extern void cstbinary(struct result *presult, char *s);
      |             ^~~~~~~~~
parse.c:99:66: error: initialization of ‘void (*)(void)’ from incompatible pointer type ‘void (*)(struct result *, char *)’ [-Wincompatible-pointer-types]
   99 |         { "0B?"         ,-2,1   /* C binaire    */              ,cstbinary,},
      |                                                                  ^~~~~~~~~
parse.c:99:66: note: (near initialization for ‘oplist[22].callop’)
parse.c:60:13: note: ‘cstbinary’ declared here
   60 | extern void cstbinary(struct result *presult, char *s);
      |             ^~~~~~~~~
pseudos.c:376:10: error: too many arguments to function ‘q->init’; expected 0, have 1
  376 |         (*q->init)(q->code);
      |         ~^~~~~~~~~ ~~~~~~~
parse.c:100:66: error: initialization of ‘void (*)(void)’ from incompatible pointer type ‘void (*)(struct result *, char *)’ [-Wincompatible-pointer-types]
  100 |         { "?Q"          ,-2,1   /* Intel octal  */              ,cstoctal,},
      |                                                                  ^~~~~~~~
In file included from pseudos.c:28:
cpu.h:51:26: note: declared here
   51 |                   void (*init)(); };
      |                          ^~~~
parse.c:100:66: note: (near initialization for ‘oplist[23].callop’)
parse.c:63:13: note: ‘cstoctal’ declared here
   63 | extern void cstoctal(struct result *presult, char *s);
      |             ^~~~~~~~
parse.c: In function ‘parse2’:
parse.c:137:30: error: too many arguments to function ‘(q + (sizetype)((long unsigned int)j * 24))->callop’; expected 0, have 2
  137 |                         (q[j].callop)(presult,&arg);
      |                         ~~~~~^~~~~~~~ ~~~~~~~
parse.c:70:16: note: declared here
   70 |         void (*callop)();       /*      (*callop)(&result,&arg )  */
      |                ^~~~~~
parse.c:143:26: error: too many arguments to function ‘q->callop’; expected 0, have 1
  143 |                         (*q->callop)(presult);
      |                         ~^~~~~~~~~~~ ~~~~~~~
parse.c:70:16: note: declared here
   70 |         void (*callop)();       /*      (*callop)(&result,&arg )  */
      |                ^~~~~~
parse.c:153:26: error: too many arguments to function ‘q->callop’; expected 0, have 2
  153 |                         (*q->callop)(presult,ca);
      |                         ~^~~~~~~~~~~ ~~~~~~~
parse.c:70:16: note: declared here
   70 |         void (*callop)();       /*      (*callop)(&result,&arg )  */
      |                ^~~~~~
parse.c:177:17: error: too many arguments to function ‘error’; expected 0, have 1
  177 |                 error ( "syntax error in an expression" );
      |                 ^~~~~   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
parse.c:32:13: note: declared here
   32 | extern void error();
      |             ^~~~~
make[2]: *** [<builtin>: parse.o] Error 1
make[2]: *** [<builtin>: pseudos.o] Error 1
make[2]: Leaving directory '/build/reproducible-path/crasm-1.8/src'
make[1]: *** [Makefile:9: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/crasm-1.8'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:11: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Message #14 received at 1096478-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 1096478-close@bugs.debian.org

Subject: Bug#1096478: fixed in crasm 1.11-1

Date: Sat, 27 Sep 2025 19:04:44 +0000

[Message part 1 (text/plain, inline)]

Source: crasm
Source-Version: 1.11-1
Done: Laszlo Boszormenyi (GCS) <gcs@debian.org>

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) <gcs@debian.org> (supplier of updated crasm 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, 27 Sep 2025 18:19:40 +0000
Source: crasm
Architecture: source
Version: 1.11-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.org>
Changed-By: Laszlo Boszormenyi (GCS) <gcs@debian.org>
Closes: 1096478
Changes:
 crasm (1.11-1) unstable; urgency=medium
 .
   * New upstream release:
     - fixes FTBFS with GCC 15 (closes: #1096478).
   * Refer online version of Free Software Foundation licence.
   * Update debhelper level to 13 .
   * Update Standards-Version to 4.7.2 .
Checksums-Sha1:
 2ee9539885a6ac18455f006132a345a93de5587a 1743 crasm_1.11-1.dsc
 5ff3d816be21e9415f44fbbf4a9e23266fdf0b78 72163 crasm_1.11.orig.tar.gz
 216fe6fdd16711d8fd6a0a0710c03921b95ad785 9236 crasm_1.11-1.debian.tar.xz
Checksums-Sha256:
 27b60645a5011cfe551d7d42fcbea5230024988ea4ec915379b90dff836ae800 1743 crasm_1.11-1.dsc
 23983da187d5cd3e4e51d2fa4fe10a734660b5cb5c02e1bd01b62915137c6866 72163 crasm_1.11.orig.tar.gz
 81bd477a5ae72894326c8abd2e2eba319aceba0d671e883c0f39cb11448d10d2 9236 crasm_1.11-1.debian.tar.xz
Files:
 c3b05821eb7d9eeeee40ae778468094f 1743 devel optional crasm_1.11-1.dsc
 981b3a403b51fd9baee074c7e8bcefbc 72163 devel optional crasm_1.11.orig.tar.gz
 54a3a2ff86f9c5ca0fc2e4b6e10c6671 9236 devel optional crasm_1.11-1.debian.tar.xz

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

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmjYLrYACgkQ3OMQ54ZM
yL/6gBAAjpALysz5HTT/vRpZZw2drvRrUoj4VzEQabXuS+OIx3m+RDuZvTLR3Dlx
nDQqkrC+plcHIdxH/dOuJhMt4N5PI7b1A3Eya5/FVhsELlcPJq93Re08YCSvpxbs
ANT0GiG1GuupKMO1JcvRupUUZ+kfvieSO2z/9UOEjpYuBpLg96RzR2itBRxEeaem
84Pi3ke4grGvm1DIIiz7pYi2szPTEDL/ioym0L745o4HYH9UKEJQC1ZdrSE7uV2b
9f8IJel3RwL80K9E8oyhNbLV4atxLCgDvu6snvay3ou1zmuM6B8dTkmlgqyTDoRc
92FlMeSvnvGcA7hpz27Rs623Fivojb36cwtvMAikMi27F9mmwC1FGZT7+/q59TlG
kn7Z5aLNcIexMS3V43JB6SHlT9WXopdkMAaq5qmQeil4o9Uzmq7Qo/6r4EliX7SK
Dyy3p255CmIHKJh9fASsYj40mJ9jSwzRIydOySiaY7QoPm2KxuQED6h24uxh7ADH
JQNWtpQ4KlNByIj7qlvmEEVXI6TQp4kw4V+BFR66BpR9hXmLgMRDqFHUT8vE459J
W8+XdsQQDEwyHjk+6M4hc8v/+uCiOnGckSiBWQIgwUvwoUxz+oycxqa8HzV88x7M
2wSAyOGpgYJrq6QIAVQMdgvUYysDv27VRuus5B80T8DW9Rhj1XA=
=B0s0
-----END PGP SIGNATURE-----

[Message part 2 (application/pgp-signature, inline)]

Message #19 received at 1096478@bugs.debian.org (full text, mbox, reply):

From: Sergio Durigan Junior <sergiodj@sergiodj.net>

To: 1096478@bugs.debian.org

Subject: Re: Bug#1096478 closed by Debian FTP Masters <ftpmaster@ftp-master.debian.org> (reply to Laszlo Boszormenyi (GCS) <gcs@debian.org>) (Bug#1096478: fixed in crasm 1.11-1)

Date: Sat, 27 Sep 2025 15:53:08 -0400

On Saturday, September 27 2025, Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the src:crasm package:
>
> #1096478: crasm: ftbfs with GCC-15

Wow, I had *just* made an NMU upload to fix crasm!  Talk about
synchronicity!

Either way, one of the things I did was to create a repository on salsa
and push the entire history for the package there (generated with "gbp
import-dscs --debsnap").  Feel free to take over it and rewrite the
history.

https://salsa.debian.org/debian/crasm

Thanks!

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

Send a report that this bug log contains spam.