Your message dated Sat, 13 Sep 2025 15:00:04 +0000
with message-id <[email protected]>
and subject line Bug#1096679: fixed in gbatnav 1.0.4cvs20051004-8
has caused the Debian Bug report #1096679,
regarding gbatnav: 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 [email protected]
immediately.)
--
1096679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096679
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:gbatnav
Version: 1.0.4cvs20051004-7
Severity: important
Tags: sid forky
User: [email protected]
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/gbatnav_1.0.4cvs20051004-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
[...]
| ^~~~~~~~~~
play.c:493:41: note: (near initialization for ‘tokens[5].func’)
play.c:315:6: note: ‘token_exit’ declared here
315 | void token_exit( int fd )
| ^~~~~~~~~~
play.c:494:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int, char *)’ [-Wincompatible-pointer-types]
494 | { BN_NAME, token_name },
| ^~~~~~~~~~
play.c:494:41: note: (near initialization for ‘tokens[6].func’)
play.c:414:13: note: ‘token_name’ declared here
414 | static void token_name( int fd, char *str )
| ^~~~~~~~~~
play.c:495:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int, char *)’ [-Wincompatible-pointer-types]
495 | { BN_FIRE, token_fire },
| ^~~~~~~~~~
play.c:495:41: note: (near initialization for ‘tokens[7].func’)
play.c:135:13: note: ‘token_fire’ declared here
135 | static void token_fire( int fd, char *str )
| ^~~~~~~~~~
play.c:496:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int, char *)’ [-Wincompatible-pointer-types]
496 | { BN_ROBOT, token_robot },
| ^~~~~~~~~~~
play.c:496:41: note: (near initialization for ‘tokens[8].func’)
play.c:71:13: note: ‘token_robot’ declared here
71 | static void token_robot( int fd, char *str )
| ^~~~~~~~~~~
play.c:499:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int, char *)’ [-Wincompatible-pointer-types]
499 | { BN_CLI_VER, token_client_version },
| ^~~~~~~~~~~~~~~~~~~~
play.c:499:41: note: (near initialization for ‘tokens[11].func’)
play.c:431:13: note: ‘token_client_version’ declared here
431 | static void token_client_version( int fd, char *str )
| ^~~~~~~~~~~~~~~~~~~~
play.c:500:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
500 | { BN_SER_VER, token_server_version },
| ^~~~~~~~~~~~~~~~~~~~
play.c:500:41: note: (near initialization for ‘tokens[12].func’)
play.c:442:13: note: ‘token_server_version’ declared here
442 | static void token_server_version( int fd )
| ^~~~~~~~~~~~~~~~~~~~
play.c:501:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
501 | { BN_NUMJUG, token_numjug },
| ^~~~~~~~~~~~
play.c:501:41: note: (near initialization for ‘tokens[13].func’)
play.c:55:13: note: ‘token_numjug’ declared here
55 | static void token_numjug( int fd )
| ^~~~~~~~~~~~
play.c:502:41: error: initialization of ‘void (*)(void)’ from incompatible
pointer type ‘void (*)(int)’ [-Wincompatible-pointer-types]
502 | { BN_HELP, token_help },
| ^~~~~~~~~~
play.c:502:41: note: (near initialization for ‘tokens[14].func’)
play.c:453:13: note: ‘token_help’ declared here
453 | static void token_help ( int fd )
| ^~~~~~~~~~
play.c:516:43: error: too many arguments to function ‘tokens[i].func’; expected
0, have 2
516 | (tokens[i].func)(fd,p->value);
| ~~~~~~~~~~^~~~~~ ~~
play.c:485:24: note: declared here
485 | void (*func) ();
| ^~~~
make[3]: *** [Makefile:535: play.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory
'/build/reproducible-path/gbatnav-1.0.4cvs20051004/gbnserver'
make[2]: *** [Makefile:471: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/gbatnav-1.0.4cvs20051004'
make[1]: *** [Makefile:399: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/gbatnav-1.0.4cvs20051004'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:9: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: gbatnav
Source-Version: 1.0.4cvs20051004-8
Done: Ying-Chun Liu (PaulLiu) <[email protected]>
We believe that the bug you reported is fixed in the latest version of
gbatnav, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu) <[email protected]> (supplier of updated gbatnav
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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 13 Sep 2025 05:37:06 +0100
Source: gbatnav
Architecture: source
Version: 1.0.4cvs20051004-8
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) <[email protected]>
Changed-By: Ying-Chun Liu (PaulLiu) <[email protected]>
Closes: 1096679
Changes:
gbatnav (1.0.4cvs20051004-8) unstable; urgency=low
.
* Fix FTBFS: port to gcc15 (Closes: #1096679)
- Update debian/patches/gcc10.patch
Checksums-Sha1:
be5b246d65b37af3b30b8a87091ef7d6b8da8fd4 1850 gbatnav_1.0.4cvs20051004-8.dsc
6218e44d94c4ae7faa06b98fcc0001c62e5bbf37 33764
gbatnav_1.0.4cvs20051004-8.debian.tar.xz
306e283962567fd259d95ad544d8e69c37d19c08 6071
gbatnav_1.0.4cvs20051004-8_source.buildinfo
Checksums-Sha256:
7a1bd6b9e774f8aa35d433148d803bade11ddaf8f8b187216c20f69e77c778d9 1850
gbatnav_1.0.4cvs20051004-8.dsc
a5a9c13c4e0f9214bdc4c28dc55104927fef1c4f316e530bc78e28ac839e354d 33764
gbatnav_1.0.4cvs20051004-8.debian.tar.xz
371f3b662f9583337b74be1ca576703eb21583141c24b7792d26394b98321fd2 6071
gbatnav_1.0.4cvs20051004-8_source.buildinfo
Files:
74289af331a0787f06d4a0415864fc27 1850 games optional
gbatnav_1.0.4cvs20051004-8.dsc
05b260505173ef323ff4fee67770928d 33764 games optional
gbatnav_1.0.4cvs20051004-8.debian.tar.xz
e2c18556ddd044aa6f9c0fc168c458e6 6071 games optional
gbatnav_1.0.4cvs20051004-8_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmjE9n0THHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiE56EACkknzdqqTiOBT3AwmW20P0DPN+X7q9
2GPQ2FWfmi8Whmn+kvHE1uIY2oqsuOOwuJGM6fWQH07v1hmHpgUsHSXrsga9zR0q
ZbZPuNH2j1UD4aFXg8KiBhfOb44N27PcAvHQ8sT1TI/0M4mab9wjUqXrDJCtb94W
HNgnyA2Yl/JhEWXReNIJmYZQmb0Ernebc4HoNicamDzyeo1l6pgUBgDGoqLbHRsG
9fwsTof2230EU5YwvYLIZDahmFQACa3koGLlQYqFRusDSdl0Pe1Q1dN0w3NG8wlS
2RlprAmncUSbIkPuThdZ0jLBtyJ+B+8HnlU1M7CHlxYn3oVd9geYaw+o/qB3TB5o
Ot/yr1DiLji+/YPnpv/dsNnuDrJN14FlnjaLmgoNdho0fuGtc1w0SniHOdGqAby6
d1cuPn6MkyHvVYLkqk63PqU1+Y+mF0neTyvTHF1h5NKaB5KSvOXSM8mmn0E8xwyb
/vAxdSpc8Wk7yKhZKMO9BO5b1Dd5KWvJoaYke1iPXldDQYkbjGUtKg2NSt/thGWJ
rUvQySLJeB7JsF+f7mI+dA82Rvie4Rb+X2vKrc81xMCvIXwFfLaZ4rq8aL/ELZ/n
MQtKjtuEGhOPAVL4QzqcAXhVRAyO3MD/EBy7mh4XdyP0oSwmcV+TLv6WtsKldGGv
zd6N2sXDBiXqPg==
=dGrY
-----END PGP SIGNATURE-----
pgps0NcHe5gyA.pgp
Description: PGP signature
--- End Message ---
