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

Bug#1097769: marked as done (rapiddisk: ftbfs with GCC-15)

Your message dated Tue, 16 Dec 2025 13:35:23 +0000
with message-id <E1vVVD1-002rOr-2Z@fasolo.debian.org>
and subject line Bug#1097769: fixed in rapiddisk 9.2.0-2
has caused the Debian Bug report #1097769,
regarding rapiddisk: 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.)


-- 
1097769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097769
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:rapiddisk
Version: 9.1.0-5
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/rapiddisk_9.1.0-5_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

[...]
   60 | typedef char bool;
      | ^~~~~~~
common.h:222:37: warning: extra semicolon in struct or union specified [-Wpedantic]
  222 | typedef struct NVMET_ALLOWED_HOST { ;
      |                                     ^
      |                                     -
common.h:222:37: warning: extra semicolon in struct or union specified [-Wpedantic]
  222 | typedef struct NVMET_ALLOWED_HOST { ;
      |                                     ^
      |                                     -
In file included from utils.h:35,
                 from rapiddiskd.c:32:
common.h:60:14: error: ‘bool’ cannot be defined via ‘typedef’
   60 | typedef char bool;
      |              ^~~~
common.h:60:14: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
common.h:60:1: warning: useless type name in empty declaration
   60 | typedef char bool;
      | ^~~~~~~
common.h:222:37: warning: extra semicolon in struct or union specified [-Wpedantic]
  222 | typedef struct NVMET_ALLOWED_HOST { ;
      |                                     ^
      |                                     -
json.c: In function ‘json_nvmet_view_exports’:
json.c:514:24: warning: unused variable ‘nvmet_orig’ [-Wunused-variable]
  514 |         NVMET_PROFILE *nvmet_orig = nvmet;
      |                        ^~~~~~~~~~
make[1]: *** [Makefile:142: rapiddiskd_ndebug.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:142: json_ndebug.o] Error 1
make[1]: *** [Makefile:142: sys_ndebug.o] Error 1
rdsk.c: In function ‘dm_flush_device’:
rdsk.c:428:21: warning: unused variable ‘response’ [-Wunused-variable]
  428 |         const char *response = dm_task_get_message_response(dmt);
      |                     ^~~~~~~~
In file included from utils.h:35,
                 from utils.c:32:
common.h:60:14: error: ‘bool’ cannot be defined via ‘typedef’
   60 | typedef char bool;
      |              ^~~~
In file included from utils.h:35,
                 from main.c:34:
common.h:60:14: error: ‘bool’ cannot be defined via ‘typedef’
   60 | typedef char bool;
      |              ^~~~
common.h:60:14: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
common.h:60:14: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
common.h:60:1: warning: useless type name in empty declaration
   60 | typedef char bool;
      | ^~~~~~~
common.h:60:1: warning: useless type name in empty declaration
   60 | typedef char bool;
      | ^~~~~~~
common.h:222:37: warning: extra semicolon in struct or union specified [-Wpedantic]
  222 | typedef struct NVMET_ALLOWED_HOST { ;
      |                                     ^
      |                                     -
common.h:222:37: warning: extra semicolon in struct or union specified [-Wpedantic]
  222 | typedef struct NVMET_ALLOWED_HOST { ;
      |                                     ^
      |                                     -
make[1]: *** [Makefile:145: utils-server_ndebug.o] Error 1
make[1]: *** [Makefile:142: main_ndebug.o] Error 1
make[1]: *** [Makefile:142: nvmet_ndebug.o] Error 1
make[1]: *** [Makefile:142: rdsk_ndebug.o] Error 1
make[1]: *** [Makefile:142: utils_ndebug.o] Error 1
make[1]: Leaving directory '/build/reproducible-path/rapiddisk-9.1.0/src'
dh_auto_build: error: cd src && make -j8 "INSTALL=install --strip-program=true" returned exit code 2
make: *** [debian/rules:15: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: rapiddisk
Source-Version: 9.2.0-2
Done: Andreas Beckmann <anbe@debian.org>

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

Debian distribution maintenance software
pp.
Andreas Beckmann <anbe@debian.org> (supplier of updated rapiddisk 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: Tue, 16 Dec 2025 13:03:38 +0100
Source: rapiddisk
Architecture: source
Version: 9.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Beckmann <anbe@debian.org>
Closes: 1097769 1109903
Changes:
 rapiddisk (9.2.0-2) unstable; urgency=medium
 .
   * QA upload.
   * Fix module build for Linux 6.16.  (Closes: #1109903)
   * Fix building with -std=c23.  (Closes: #1097769)
   * Drop redundant Rules-Requires-Root: no.
Checksums-Sha1:
 c98f2e86df786c241752288cafd1d6d8c9c71943 2039 rapiddisk_9.2.0-2.dsc
 2bcdb700f4df4629ac34d44dc37718ef27222e75 4764 rapiddisk_9.2.0-2.debian.tar.xz
 d6d586c202fa5c89c17666b5cffbb685eeaafd05 6475 rapiddisk_9.2.0-2_source.buildinfo
Checksums-Sha256:
 aef11ee715ba8e2fe1e3b97b17bc37b97aa113dc1c041aec073b3346fc329683 2039 rapiddisk_9.2.0-2.dsc
 0b28c46b3fbe70a0d337ea18500ec70b79641e7960838aa803326c23db3c2dc3 4764 rapiddisk_9.2.0-2.debian.tar.xz
 e61677c087835b1f5350321d597193070799e69b6c185e5a78d570d38b452ddb 6475 rapiddisk_9.2.0-2_source.buildinfo
Files:
 dab1f10dc3f68ca4c30b4b2e54a1dd75 2039 kernel optional rapiddisk_9.2.0-2.dsc
 59157409f8fad45e03a40294659ae94c 4764 kernel optional rapiddisk_9.2.0-2.debian.tar.xz
 d79aa864462013e251dcdf65635a7bf3 6475 kernel optional rapiddisk_9.2.0-2_source.buildinfo

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

iQJEBAEBCgAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmlBTO8QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCJwaEACS1OCToHZwQkhDjCw6VGV1yC1l/Z9l9LiI
onq3Z2ycL58DeUkEB7F4XWsD04imlzreMdRuigSHt7AvWgCkP6rXbf3NyHoOuekp
J0EJxW5s5tzo0mxAS2RQufuwvbo6pWGe8nvlU+hVIEXkz29WSb8iEvHNRCtUMn/C
5J2HTHrrCPmBA/wvrWBaQWgWZ6dWjA8WcUW2pJ5MzuQbujUVAtH04MSO0xJi7CPK
cdcHYcKXWu7De2LxoMIF/oQA8aaUJhi6nGUuG7QeDOfNfar3vBy3dKNNVqgKkOc+
YKL/3VOFTC4f0E7mB1pHLQt0CLdoqFBDzE0lIQAmqCgtv6hX85zEpONYpgS/w3IQ
fTgEW+1/aKcPmhMJEVmcl29Crd1sVaTsSSnVq+ETOv9sF2yKpT0kBf69OZvlwbup
aq+YUvqEutle61a4g4SgQAzx2Qxace2zdInzRPVVRHDeAOx9QIs1UDqkqolj7P8F
iZqe7uxnK5x07B1BEUal3VcrffofaKKvSfnBJGi1aLuGZrqHcKn8aFyL/z0DHUGh
d18iASWUNTlgTzNbooT6VPdtkuoHKg2uAbwsnCvPNMbyVRFvNx1KeRtp3MRmGefI
IFbNLm869612KCRIBsGXac2Q+EVXbQy8HZ3c4O/GeunypVfSGh489Eutns+0Anm9
4K3xThxRjw==
=gq6v
-----END PGP SIGNATURE-----

Attachment: pgp3ZIXspw8L7.pgp
Description: PGP signature


--- End Message ---
Reply to: