Your message dated Wed, 05 Nov 2025 10:34:26 +0000
with message-id <[email protected]>
and subject line Bug#1096430: fixed in chasen 2.4.5-46.1
has caused the Debian Bug report #1096430,
regarding chasen: 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.)


-- 
1096430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096430
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:chasen
Version: 2.4.5-46
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/chasen_2.4.5-46_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

[...]
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
chalib.c: In function 'cha_read_dadic':
chalib.c:618:43: warning: '%s' directive output may be truncated writing up to 
131071 bytes into a region of size 4096 [-Wformat-truncation=]
  618 |         snprintf(dat_filename, PATH_MAX, "%s.dat", dadic_filename[num]);
      |                                           ^~
In function 'snprintf',
    inlined from 'cha_read_dadic' at chalib.c:618:2:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: 
'__builtin___snprintf_chk' output between 5 and 131076 bytes into a destination 
of size 4096
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
libtool: compile:  gcc -DRCPATH=\"/etc/chasenrc\" -DHAVE_CONFIG_H -I. -I.. -I.. 
-I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/chasen-2.4.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wall -c chalib.c -o chalib.o 
>/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc 
-DRCPATH="\"/etc/chasenrc\"" -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/include   
-Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/chasen-2.4.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wall -c -o connect.lo connect.c
libtool: compile:  gcc -DRCPATH=\"/etc/chasenrc\" -DHAVE_CONFIG_H -I. -I.. -I.. 
-I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-Werror=implicit-function-declaration 
-ffile-prefix-map=/build/reproducible-path/chasen-2.4.5=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wall -c connect.c  -fPIC -DPIC -o 
.libs/connect.o
connect.c: In function 'cha_check_table':
connect.c:206:15: error: passing argument 4 of 'qsort' from incompatible 
pointer type [-Wincompatible-pointer-types]
  206 |               (int (*)()) cmp_pair);
      |               ^~~~~~~~~~~~~~~~~~~~
      |               |
      |               int (*)(void)
In file included from chadic.h:14,
                 from connect.c:33:
/usr/include/stdlib.h:971:34: note: expected '__compar_fn_t' {aka 'int 
(*)(const void *, const void *)'} but argument is of type 'int (*)(void)'
  971 |                    __compar_fn_t __compar) __nonnull ((1, 4));
      |                    ~~~~~~~~~~~~~~^~~~~~~~
/usr/include/stdlib.h:948:15: note: '__compar_fn_t' declared here
  948 | typedef int (*__compar_fn_t) (const void *, const void *);
      |               ^~~~~~~~~~~~~
connect.c:210:41: error: passing argument 5 of 'bsearch' from incompatible 
pointer type [-Wincompatible-pointer-types]
  210 |                 sizeof(rensetu_pair_t), (int (*)()) find_table);
      |                                         ^~~~~~~~~~~~~~~~~~~~~~
      |                                         |
      |                                         int (*)(void)
In file included from /usr/include/stdlib.h:965:
/usr/include/x86_64-linux-gnu/bits/stdlib-bsearch.h:21:24: note: expected 'int 
(*)(const void *, const void *)' but argument is of type 'int (*)(void)'
   21 |          __compar_fn_t __compar)
      |          ~~~~~~~~~~~~~~^~~~~~~~
connect.c:218:41: error: passing argument 5 of 'bsearch' from incompatible 
pointer type [-Wincompatible-pointer-types]
  218 |                 sizeof(rensetu_pair_t), (int (*)()) find_table);
      |                                         ^~~~~~~~~~~~~~~~~~~~~~
      |                                         |
      |                                         int (*)(void)
/usr/include/x86_64-linux-gnu/bits/stdlib-bsearch.h:21:24: note: expected 'int 
(*)(const void *, const void *)' but argument is of type 'int (*)(void)'
   21 |          __compar_fn_t __compar)
      |          ~~~~~~~~~~~~~~^~~~~~~~
connect.c: In function 'cha_read_table':
connect.c:126:5: warning: ignoring return value of 'fscanf' declared with 
attribute 'warn_unused_result' [-Wunused-result]
  126 |     fscanf(fp, "%d\n", &cell_num);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
connect.c: In function 'cha_read_matrix':
connect.c:261:5: warning: ignoring return value of 'fscanf' declared with 
attribute 'warn_unused_result' [-Wunused-result]
  261 |     fscanf(fp, "%d %d\n", &i_num, &j_num);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[3]: *** [Makefile:498: connect.lo] Error 1
make[3]: Leaving directory '/build/reproducible-path/chasen-2.4.5/lib'
make[2]: *** [Makefile:487: all-recursive] Error 1
make[2]: Leaving directory '/build/reproducible-path/chasen-2.4.5'
make[1]: *** [Makefile:380: all] Error 2
make[1]: Leaving directory '/build/reproducible-path/chasen-2.4.5'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: chasen
Source-Version: 2.4.5-46.1
Done: Adrian Bunk <[email protected]>

We believe that the bug you reported is fixed in the latest version of
chasen, 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.
Adrian Bunk <[email protected]> (supplier of updated chasen 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: Tue, 21 Oct 2025 12:28:38 +0300
Source: chasen
Architecture: source
Version: 2.4.5-46.1
Distribution: unstable
Urgency: medium
Maintainer: "Natural Language Processing (Japanese)" 
<[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1096430
Changes:
 chasen (2.4.5-46.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with GCC 15, thanks to Florian Ernst. (Closes: #1096430)
Checksums-Sha1:
 8dfddbfe9e0cf93edf8757910c33172e43f71cdf 2167 chasen_2.4.5-46.1.dsc
 602aca2707728a096932b3bd6d0f16aa334293a5 13424 chasen_2.4.5-46.1.debian.tar.xz
Checksums-Sha256:
 2f5e716ef9224acadd23d7767e0e06798c308401ebc2be34d3fd41cb5ff58f63 2167 
chasen_2.4.5-46.1.dsc
 5db62784feff276f87b4131903575bf52c40362aba6c9de67a570020d14e4920 13424 
chasen_2.4.5-46.1.debian.tar.xz
Files:
 551c6c175f49d9b941cf9b5f40d33c5f 2167 misc optional chasen_2.4.5-46.1.dsc
 67236a5eecb660617250d4dbd0d289a7 13424 misc optional 
chasen_2.4.5-46.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmj3VC4ACgkQiNJCh6LY
mLGV5Q/5ARXZbeJwtQdkOsNw5dfvhUyrSHFTQl4wq2BWXcrNaUaxUqwi9WnVYvUT
Ixji7mEY2IHbm3qOE6kw/hAz7Z7XMKvQ0cnBiEEwXYV1q0IPAMlveD+adQ6UuRX3
SnbtZTBygA/nxObreZjc9qeqrtcTbzaXFj/z+pgv7pnF3PzbRjj6Qaj0ye45KYc3
OIWqRAH0pUmk6Q/kIAYRMUt15oC8N2rxEXd2hezhh4NHmtlXpxaMlfhd7oZYuk5x
i2dsS0Dkdz2Ck+vLPKYYDmbsInszF0LNJAYd06YiSFe8bL9xhPdCIyNtl7QOAARf
m+Re++GEUdjTTNs8kaDk2Nft5eGhKLPtbum2PdRrmIIuTWTXYtj25VCnArc7M+wD
AfmFK0C22xCehi0Vwb77+Q9h6XK4YQmRXBBOmlwiTTaY33mWH1H8yvg1G45KB0z8
0veigCRvcWPnKbYlbDlNTmJ/9vKbh2XkL75zG3wWEYq31RF9gSBchIp656RlmFFK
7x/N7YUjHjOejPOZKMolialQ3uZ6Btrkkm6XFnrT1FYvZBtxPH8OXcQdZev0rXMM
h66m3zDoKWa6Smnr8JqXLuj//fPWhp6wYB16NuZjtfj06CCnYBwpf2BlYH3FWxQk
4BPAWnrCtF5A/c8TXJ5X0lr7y6IOtj8rvLMPgbAM5EjBYnx30JU=
=NHVf
-----END PGP SIGNATURE-----

Attachment: pgp7Jh8B2uYlz.pgp
Description: PGP signature


--- End Message ---

Reply via email to