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

Bug#1096411: marked as done (canna: ftbfs with GCC-15)

Your message dated Sat, 04 Oct 2025 22:34:03 +0000
with message-id <E1v5ApH-009O6w-0r@fasolo.debian.org>
and subject line Bug#1096411: fixed in canna 3.7p3-26
has caused the Debian Bug report #1096411,
regarding canna: 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.)


-- 
1096411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096411
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:canna
Version: 3.7p3-25
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/canna_3.7p3-25_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

[...]
  984 | void                    _RkKillCache();
      |                         ^~~~~~~~~~~~
tempdic.c: In function ‘_Rktsearch’:
tempdic.c:608:1: warning: old-style function definition [-Wold-style-definition]
  608 | _Rktsearch(cx, dm, key, n, nread, maxcache, cf)
      | ^~~~~~~~~~
tempdic.c:624:21: error: too many arguments to function ‘uniqAlnum’; expected 0, have 1
  624 |     Wchar       k = uniqAlnum(key[j++]);
      |                     ^~~~~~~~~ ~~~~~~~~
tempdic.c:617:17: note: declared here
  617 |   Wchar         uniqAlnum();
      |                 ^~~~~~~~~
tempdic.c:643:33: error: too many arguments to function ‘_RkReadCache’; expected 0, have 2
  643 |               nread[nc].cache = _RkReadCache(dm, (long)tn->tn_word);
      |                                 ^~~~~~~~~~~~ ~~
RKintern.h:982:26: note: declared here
  982 | struct ncache           *_RkReadCache();
      |                          ^~~~~~~~~~~~
tempdic.c:671:35: error: too many arguments to function ‘_RkReadCache’; expected 0, have 2
  671 |                 nread[nc].cache = _RkReadCache(dm, (long)n0->tn_word);
      |                                   ^~~~~~~~~~~~ ~~
RKintern.h:982:26: note: declared here
  982 | struct ncache           *_RkReadCache();
      |                          ^~~~~~~~~~~~
tempdic.c: In function ‘_Rktio’:
tempdic.c:702:1: warning: old-style function definition [-Wold-style-definition]
  702 | _Rktio(dm, cp, io)
      | ^~~~~~
tempdic.c: In function ‘_Rktctl’:
tempdic.c:720:1: warning: old-style function definition [-Wold-style-definition]
  720 | _Rktctl(dm, qm, what, arg, gram)
      | ^~~~~~~
tempdic.c:746:15: error: too many arguments to function ‘RkParseOWrec’; expected 0, have 5
  746 |     else if (!RkParseOWrec(gram, arg, wrec, TEMPDIC_WRECSIZE, lucks))
      |               ^~~~~~~~~~~~ ~~~~
RKintern.h:1001:26: note: declared here
 1001 | Wrec                    *RkParseOWrec();
      |                          ^~~~~~~~~~~~
tempdic.c:758:15: error: too many arguments to function ‘RkParseOWrec’; expected 0, have 5
  758 |     else if (!RkParseOWrec(gram, arg, wrec, TEMPDIC_WRECSIZE, lucks))
      |               ^~~~~~~~~~~~ ~~~~
RKintern.h:1001:26: note: declared here
 1001 | Wrec                    *RkParseOWrec();
      |                          ^~~~~~~~~~~~
tempdic.c: In function ‘_Rktsync’:
tempdic.c:774:1: warning: old-style function definition [-Wold-style-definition]
  774 | _Rktsync(cx, dm, qm)
      | ^~~~~~~~
tempdic.c:807:11: error: too many arguments to function ‘_RkCreatePath’; expected 0, have 2
  807 |   file  = _RkCreatePath(dd_p, df_p->df_link);
      |           ^~~~~~~~~~~~~ ~~~~
RKintern.h:1060:26: note: declared here
 1060 | char                    *_RkCreatePath();
      |                          ^~~~~~~~~~~~~
tempdic.c: At top level:
tempdic.c:24:13: warning: ‘rcsid’ defined but not used [-Wunused-variable]
   24 | static char rcsid[]="$Id: tempdic.c,v 1.4 2003/09/17 08:50:52 aida_s Exp $";
      |             ^~~~~
make[5]: *** [Makefile:1123: tempdic.o] Error 1
make[5]: Leaving directory '/build/reproducible-path/canna-3.7p3/lib/RK'
make[4]: *** [Makefile:1112: all] Error 2
make[4]: Leaving directory '/build/reproducible-path/canna-3.7p3/lib'
make[3]: *** [Makefile:1120: all] Error 2
make[3]: Leaving directory '/build/reproducible-path/canna-3.7p3'
make[2]: *** [Makefile:1263: canna] Error 2
make[2]: Leaving directory '/build/reproducible-path/canna-3.7p3'
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/reproducible-path/canna-3.7p3'
make: *** [debian/rules:74: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: canna
Source-Version: 3.7p3-26
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
canna, 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 1096411@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated canna 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 04 Oct 2025 21:41:22 +0300
Source: canna
Architecture: source
Version: 3.7p3-26
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1096411
Changes:
 canna (3.7p3-26) unstable; urgency=medium
 .
   * QA upload.
   * Build with -std=gnu17 to workaround FTBFS with GCC 15.
     (Closes: #1096411)
Checksums-Sha1:
 57f9b9db613f8088fd11745edbf6d8c9434b1702 2033 canna_3.7p3-26.dsc
 6292203aeaed912fed5d14cc97db47b89ea55fd6 82204 canna_3.7p3-26.debian.tar.xz
Checksums-Sha256:
 8caeee93b5fe6f70852febacb7f12139bb33fe16140b9f7589b7bc8096883faf 2033 canna_3.7p3-26.dsc
 f62b59f1aac22a9c9b289c4e6ca09848abd961d14a08653f05751dd4c5bfc769 82204 canna_3.7p3-26.debian.tar.xz
Files:
 5c99cc317f1c36f35700fb716b70af39 2033 utils optional canna_3.7p3-26.dsc
 1930f60b879a3651d5c524b842d8ecfc 82204 utils optional canna_3.7p3-26.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjhnkUACgkQiNJCh6LY
mLGjLw/9H9r1GFqYVdtcY8CdxuDef1llqRBbiq2/mqtnzwr0WMmqbIaBqg4r3lvF
W6YMIGcJj1MQMM7RzXXQvIzwzRlFaqSCnctJI8VwuBnzZ4NcjB2DW5cVGIUnlfdt
RK0PYhWVsW+EDr2sgS0tOHGP27OAbwGjU9MxlL/jPAUU4epeOO9C9QmoSjxZ6IX+
SzLQvnXnDInnrvOOTZJHyQksYghqAhvsnWrZeAo9KGltT2gt86KPcifBx1QDsk6t
ImBvpzUYSVCQR8yGMxcvN6cwuJCNm8qK7KNR+kOfjuBuUODay7unvdYZVLQns/Ry
pky7UjFNjetmJ2AWR9eVhAYaJnfCTJOCQuZRTyldgmlRUi1Mv6puBixryLrSvC9o
9K//DPPzHgXasOSQ/JrBxcEf5HxptZBEe25q7mqnt7G5Ar1EbjcwOCF5tsQQ6/5+
LuRdP0ydr5XBGyO41LuulE1Wi1fC2zjYWEHU/O4/xeOdkLKMCpbxW2XUF5ZBlaTe
GqyehSAU5Oir/27F3XrvDtDtrZwaYNXhY0xsHIfgEdy9//U1NgAV6aprHakcxWjS
/Cr2Ck7mD9wZg4SF4iUJymZb3hdRFc8+uzGicENLRv6h1OaIaKJGGi7D0Ru3AR8U
euMgFobmLIN5z2XD3Ey55LUXzHbEGcGT28lQI51WIllzMoMM4Is=
=u8B5
-----END PGP SIGNATURE-----

Attachment: pgpdlfyDeeJgY.pgp
Description: PGP signature


--- End Message ---
Reply to: