Your message dated Fri, 2 May 2025 18:00:22 +0200
with message-id <[email protected]>
and subject line fixed in 1:1.0.51-15
has caused the Debian Bug report #1097410,
regarding moon-buggy: 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.)
--
1097410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097410
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:moon-buggy
Version: 1:1.0.51-14
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/moon-buggy_1.0.51-14_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
[...]
81 | install_signal (signum, generic_handler);
| ^~~~~~~~~~~~~~~
| |
| void (*)(int)
signal.c:50:42: note: expected ‘void (*)(void)’ but argument is of type ‘void
(*)(int)’
50 | install_signal (int signum, RETSIGTYPE (*handler) ())
signal.c:64:1: note: ‘generic_handler’ declared here
64 | generic_handler (int signum)
| ^~~~~~~~~~~~~~~
signal.c: In function ‘my_signal’:
signal.c:104:27: error: passing argument 2 of ‘install_signal’ from
incompatible pointer type [-Wincompatible-pointer-types]
104 | install_signal (signum, generic_handler);
| ^~~~~~~~~~~~~~~
| |
| void (*)(int)
signal.c:50:42: note: expected ‘void (*)(void)’ but argument is of type ‘void
(*)(int)’
50 | install_signal (int signum, RETSIGTYPE (*handler) ())
signal.c:64:1: note: ‘generic_handler’ declared here
64 | generic_handler (int signum)
| ^~~~~~~~~~~~~~~
signal.c: In function ‘tstp_handler’:
signal.c:126:28: error: passing argument 2 of ‘install_signal’ from
incompatible pointer type [-Wincompatible-pointer-types]
126 | install_signal (SIGTSTP, SIG_DFL);
| ^~~~~~~
| |
| void (*)(int)
signal.c:50:42: note: expected ‘void (*)(void)’ but argument is of type ‘void
(*)(int)’
50 | install_signal (int signum, RETSIGTYPE (*handler) ())
signal.c: In function ‘cont_handler’:
signal.c:133:28: error: passing argument 2 of ‘install_signal’ from
incompatible pointer type [-Wincompatible-pointer-types]
133 | install_signal (SIGTSTP, tstp_handler);
| ^~~~~~~~~~~~
| |
| void (*)(int)
signal.c:50:42: note: expected ‘void (*)(void)’ but argument is of type ‘void
(*)(int)’
50 | install_signal (int signum, RETSIGTYPE (*handler) ())
signal.c:121:1: note: ‘tstp_handler’ declared here
121 | tstp_handler (int signum)
| ^~~~~~~~~~~~
make[3]: *** [Makefile:550: signal.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from /usr/include/string.h:548,
from highscore.c:17:
In function ‘strncat’,
inlined from ‘read_version2_data’ at highscore.c:210:5,
inlined from ‘read_data’ at highscore.c:273:11,
inlined from ‘update_score_file’ at highscore.c:450:22:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:149:10: warning:
‘__strncat_chk’ specified bound 40 equals destination size
[-Wstringop-overflow=]
149 | return __builtin___strncat_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
150 | __glibc_objsize (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘strncat’,
inlined from ‘read_version3_data’ at highscore.c:244:5,
inlined from ‘read_data’ at highscore.c:276:11,
inlined from ‘update_score_file’ at highscore.c:450:22:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:149:10: warning:
‘__strncat_chk’ specified bound 40 equals destination size
[-Wstringop-overflow=]
149 | return __builtin___strncat_chk (__dest, __src, __len,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
150 | __glibc_objsize (__dest));
| ~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:149:10: warning:
‘__strncat_chk’ specified bound 40 equals destination size
[-Wstringop-overflow=]
make[3]: Leaving directory '/build/reproducible-path/moon-buggy-1.0.51'
make[2]: *** [Makefile:408: all] Error 2
make[2]: Leaving directory '/build/reproducible-path/moon-buggy-1.0.51'
dh_auto_build: error: make -j8 returned exit code 2
make[1]: *** [debian/rules:25: override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/reproducible-path/moon-buggy-1.0.51'
make: *** [debian/rules:15: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Package: moon-buggy
Version: 1:1.0.51-15
Fixed in new upload by adding the correct parameter to the function declarator.
--- End Message ---
