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

Bug#1096781: marked as done (gross: ftbfs with GCC-15)

Your message dated Tue, 23 Dec 2025 22:19:14 +0100
with message-id <aUsHUp6R91MBNa-H@an3as.eu>
and subject line Re: Bug#1096781: fixed in gross
has caused the Debian Bug report #1096781,
regarding gross: 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.)


-- 
1096781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096781
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:gross
Version: 1.0.2-4.1
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/gross_1.0.2-4.1_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

[...]
/bin/bash ../libtool --tag=CC   --mode=compile cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o grosscheck.lo grosscheck.c
mkdir .libs
 cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c grosscheck.c  -fPIC -DPIC -o .libs/grosscheck.o
 cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c grosscheck.c -o grosscheck.o >/dev/null 2>&1
/bin/bash ../libtool --tag=CC   --mode=compile cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o proto_sjsms.lo proto_sjsms.c
 cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c proto_sjsms.c  -fPIC -DPIC -o .libs/proto_sjsms.o
proto_sjsms.c: In function ‘recvquerystr’:
proto_sjsms.c:93:47: warning: ‘__builtin_snprintf’ output may be truncated before the last format character [-Wformat-truncation=]
   93 |         snprintf(querystr, MAXLINELEN - 1, "%s", message->message);
      |                                               ^
In file included from /usr/include/stdio.h:970,
                 from ../include/common.h:45,
                 from ../include/proto_sjsms.h:23,
                 from proto_sjsms.c:23:
In function ‘snprintf’,
    inlined from ‘recvquerystr’ at proto_sjsms.c:93:2:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: ‘__builtin_snprintf’ output between 1 and 1024 bytes into a destination of size 1023
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
 cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c proto_sjsms.c -o proto_sjsms.o >/dev/null 2>&1
/bin/bash ../libtool --tag=CC   --mode=link cc  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -module -avoid-version -XCClinker -static-libgcc -Wl,-z,relro -L/usr/local/lib -o grosscheck.la -rpath /usr/lib/x86_64-linux-gnu grosscheck.lo proto_sjsms.lo  -lcares -lm  -lpthread
cc -shared  .libs/grosscheck.o .libs/proto_sjsms.o  -L/usr/local/lib -lcares -lm -lpthread  -static-libgcc -Wl,-z -Wl,relro -Wl,-soname -Wl,grosscheck.so -o .libs/grosscheck.so
ar cru .libs/grosscheck.a  grosscheck.o proto_sjsms.o
ar: `u' modifier ignored since `D' is the default (see `U')
ranlib .libs/grosscheck.a
creating grosscheck.la
(cd .libs && rm -f grosscheck.la && ln -s ../grosscheck.la grosscheck.la)
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c gclient.c
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c utils.c
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c client_postfix.c
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c client_sjsms.c
/bin/bash ../libtool --tag=CC   --mode=link cc  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-z,relro -L/usr/local/lib proto_sjsms.o -Wl,-z,relro -L/usr/local/lib -o gclient gclient.o utils.o client_postfix.o client_sjsms.o  -lcares -lm  -lpthread
cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-z -Wl,relro proto_sjsms.o -Wl,-z -Wl,relro -o gclient gclient.o utils.o client_postfix.o client_sjsms.o  -L/usr/local/lib -lcares -lm -lpthread
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c sha256.c
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c bloom.c
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c srvutils.c
srvutils.c: In function ‘build_bloom_ring’:
srvutils.c:264:88: warning: format ‘%d’ expects argument of type ‘int’, but argument 3 has type ‘size_t’ {aka ‘long unsigned int’} [-Wformat=]
  264 |                         printf("statefile size (%d) differs from the calculated size (%d)\n",
      |                                                                                       ~^
      |                                                                                        |
      |                                                                                        int
      |                                                                                       %ld
  265 |                             ((int)statbuf.st_size), lumpsize);
      |                                                     ~~~~~~~~                            
      |                                                     |
      |                                                     size_t {aka long unsigned int}
cc -DHAVE_CONFIG_H -I. -I.. -I../include -D_REENTRANT -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/local/include  -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/gross-1.0.2=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c worker.c
worker.c: In function ‘test_tuple’:
worker.c:281:25: error: too many arguments to function ‘edict_get’; expected 0, have 1
  281 |                 edict = edict_get(false);
      |                         ^~~~~~~~~ ~~~~~
In file included from ../include/common.h:86,
                 from worker.c:21:
../include/thread_pool.h:113:10: note: declared here
  113 | edict_t *edict_get();
      |          ^~~~~~~~~
make[3]: *** [Makefile:424: worker.o] Error 1
make[3]: Leaving directory '/build/reproducible-path/gross-1.0.2/src'
make[2]: *** [Makefile:288: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/gross-1.0.2'
make[1]: *** [Makefile:201: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/gross-1.0.2'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:8: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Hi Omar,

Am Tue, Dec 23, 2025 at 05:51:43PM -0300 schrieb Omar:
> The the bug number was incorrectly written in this commit: https://salsa.debian.org/debian/gross/-/commit/45010cda5268521e76c5de7660fe20f5f4a05131
> ,
> 
> it should be #1096781
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096781)

Ahhhh, thanks a lot for watching me!
 
> Therefore, the bug is still open. Could you please fix the changelog file?

Fixing the changelog file after uploading is not possible ... but for sure
I can close this bug hereby with the mail interface.

Thanks a lot again
   Andreas.

-- 
https://fam-tille.de

--- End Message ---
Reply to: