Your message dated Mon, 29 Sep 2025 19:21:01 +0000
with message-id <[email protected]>
and subject line Bug#1098147: fixed in xjdic 24-13
has caused the Debian Bug report #1098147,
regarding xjdic: 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.)


-- 
1098147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098147
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:xjdic
Version: 24-12
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/xjdic_24-12_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

[...]
dh_testroot
rm -f build-stamp configure-stamp
# Add here commands to clean up after the build process.
/usr/bin/make realclean
make[1]: Entering directory '/build/reproducible-path/xjdic-24'
rm -f *.o
rm -f xjdic_sa xjdic_cl xjdserver xjdxgen exjdxgen xjdrad
make[1]: Leaving directory '/build/reproducible-path/xjdic-24'
rm -f xjdic24.txt
dh_clean
dh_clean: warning: Use of debian/compat is deprecated and will be removed in 
debhelper (>= 14~).
 debian/rules binary
dh_testdir
# Add here commands to configure the package.
touch configure-stamp
dh_testdir
# Add here commands to compile the package.
/usr/bin/make CC="x86_64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/xjdic-24=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-fcommon -O3 -Wl,-z,relro"
make[1]: Entering directory '/build/reproducible-path/xjdic-24'
x86_64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/xjdic-24=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-fcommon -O3 -Wl,-z,relro -c -DXJDFRONTEND -DXJDDIC -DMMAP xjdsa.c
x86_64-linux-gnu-gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/xjdic-24=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-fcommon -O3 -Wl,-z,relro -c -DXJDFRONTEND -DXJDDIC -DMMAP xjdcomm.c -o 
xjdcomm_sa.o
xjdcomm.c: In function ‘xfopen’:
xjdcomm.c:110:20: error: conflicting types for ‘fopen’; have ‘FILE *(void)’
  110 |         FILE *fx, *fopen();
      |                    ^~~~~
In file included from xjdcomm.c:21:
/usr/include/stdio.h:264:14: note: previous declaration of ‘fopen’ with type 
‘FILE *(const char * restrict,  const char * restrict)’
  264 | extern FILE *fopen (const char *__restrict __filename,
      |              ^~~~~
xjdcomm.c:125:14: error: too many arguments to function ‘fopen’; expected 0, 
have 2
  125 |         fx = fopen(fnbuff,file_mode);
      |              ^~~~~ ~~~~~~
xjdcomm.c:110:20: note: declared here
  110 |         FILE *fx, *fopen();
      |                    ^~~~~
xjdcomm.c:138:14: error: too many arguments to function ‘fopen’; expected 0, 
have 2
  138 |         fx = fopen(file_name,file_mode);
      |              ^~~~~ ~~~~~~~~~
xjdcomm.c:110:20: note: declared here
  110 |         FILE *fx, *fopen();
      |                    ^~~~~
xjdcomm.c: In function ‘xjdicrc’:
xjdcomm.c:195:30: error: too many arguments to function ‘fopen’; expected 0, 
have 2
  195 |                         fm = fopen(cl_rcfile,"r");
      |                              ^~~~~ ~~~~~~~~~
xjdcomm.c:169:19: note: declared here
  169 |         FILE *fm,*fopen();
      |                   ^~~~~
xjdcomm.c:214:22: error: too many arguments to function ‘fopen’; expected 0, 
have 2
  214 |                 fm = fopen(xjdicdir,"r");
      |                      ^~~~~ ~~~~~~~~
xjdcomm.c:169:19: note: declared here
  169 |         FILE *fm,*fopen();
      |                   ^~~~~
xjdcomm.c:217:22: error: too many arguments to function ‘fopen’; expected 0, 
have 2
  217 |                 fm = fopen(xjdicdir,"r");
      |                      ^~~~~ ~~~~~~~~
xjdcomm.c:169:19: note: declared here
  169 |         FILE *fm,*fopen();
      |                   ^~~~~
xjdcomm.c:224:30: error: too many arguments to function ‘fopen’; expected 0, 
have 2
  224 |                         fm = fopen(xjdicdir,"r");
      |                              ^~~~~ ~~~~~~~~
xjdcomm.c:169:19: note: declared here
  169 |         FILE *fm,*fopen();
      |                   ^~~~~
make[1]: *** [Makefile:90: xjdcomm_sa.o] Error 1
make[1]: Leaving directory '/build/reproducible-path/xjdic-24'
make: *** [debian/rules:44: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: xjdic
Source-Version: 24-13
Done: Ludovic Drolez <[email protected]>

We believe that the bug you reported is fixed in the latest version of
xjdic, 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.
Ludovic Drolez <[email protected]> (supplier of updated xjdic 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: SHA256

Format: 1.8
Date: Mon, 29 Sep 2025 20:31:43 +0200
Source: xjdic
Architecture: source
Version: 24-13
Distribution: unstable
Urgency: medium
Maintainer: Ludovic Drolez <[email protected]>
Changed-By: Ludovic Drolez <[email protected]>
Closes: 1098147
Changes:
 xjdic (24-13) unstable; urgency=medium
 .
   * GCC-15 fix. Closes: #1098147
Checksums-Sha1:
 c1796e7df8c7fcb0c888e1bb7e0a84b78073b231 1323 xjdic_24-13.dsc
 ee13f93005ccb6c80977cbd6d863bc8e1f5e47ab 13152 xjdic_24-13.debian.tar.xz
 d18e902fc66db5e38b3ef3fc45daf70d69ee1efb 5348 xjdic_24-13_amd64.buildinfo
Checksums-Sha256:
 e02c153c9d435c73568987d3c23f9b6273332d8a19e78002dd385e3d8a69fcaa 1323 
xjdic_24-13.dsc
 d2fc0a9de1444a6aa3db6f3edfdb6be111f5344b24373d2012906aae1127d858 13152 
xjdic_24-13.debian.tar.xz
 8df2f46ebd72cfb0e4b1c1ff34dc4c19814d39dac0d25fb12fdbe7feca18de5c 5348 
xjdic_24-13_amd64.buildinfo
Files:
 d5aa4423c1bf7a5022ac709188edd02c 1323 text optional xjdic_24-13.dsc
 bfb512b5ef845c9deec0a9a98ceeeed9 13152 text optional xjdic_24-13.debian.tar.xz
 7f83590f9b09d9f5439849df0d210813 5348 text optional xjdic_24-13_amd64.buildinfo

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

iQFHBAEBCAAxFiEEKrWNbKjxjlSqtxlZi3UoEkf5wXwFAmja2SwTHGxkcm9sZXpA
ZGViaWFuLm9yZwAKCRCLdSgSR/nBfLfcCACtVt/KtFRFPWp0XaolxI2oVrw5FvMH
PZ36WbUuDcmEb7bsLrPZmMW81S5Qf2KM1oetbHa54cEDrIZ5WBIoojFDBQ5DXGiZ
G2pkUBSpLWdB90WfQbAG4kPrKLUdFNkQtXK7WlG49EX+bIdc3jt1d1IVgQG9Q+xg
qWlgiwXGA9wH49x4GYuvHaEgOnQWu8ce6ol6JN2a3iqQdWQtUcDlFzrpoN3KU6XH
tMkjiDGw6vgdCbdZP/SP6x9SMheY+givg4kJqLp5plZRv7jjMPIC9O5BaDxXHmRa
Wz9LL8KlD79JYs5ruNqGzdBd9J7y6MMGCAhgCzpJo8npPkGnFm7D5wbw
=X7tj
-----END PGP SIGNATURE-----

Attachment: pgpqkiQjl1bIo.pgp
Description: PGP signature


--- End Message ---

Reply via email to