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

Bug#1097193: marked as done (libhbaapi: ftbfs with GCC-15)

Your message dated Sun, 07 Dec 2025 10:19:22 +0000
with message-id <E1vSBrO-00A4B1-0E@fasolo.debian.org>
and subject line Bug#1097193: fixed in libhbaapi 2.2.9-5
has caused the Debian Bug report #1097193,
regarding libhbaapi: 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.)


-- 
1097193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1097193
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:libhbaapi
Version: 2.2.9-4
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/libhbaapi_2.2.9-4_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

[...]
hbaapilib.c:1070:10: error: too many arguments to function 'cbp->callback'; expected 0, have 3
 1070 |         (*cbp->callback)(data, PortWWN, HBA_EVENT_ADAPTER_ADD);
      |         ~^~~~~~~~~~~~~~~ ~~~~
hbaapilib.c:210:35: note: declared here
  210 |     void                        (*callback)();
      |                                   ^~~~~~~~
hbaapilib.c: In function 'HBA_RegisterForAdapterAddEvents':
hbaapilib.c:1113:19: error: assignment to 'void (*)(void)' from incompatible pointer type 'void (*)(void *, HBA_WWN,  HBA_UINT32)' {aka 'void (*)(void *, struct HBA_wwn,  unsigned int)'} [-Wincompatible-pointer-types]
 1113 |     cbp->callback = callback;
      |                   ^
hbaapilib.c: In function 'adapterevents_callback':
hbaapilib.c:1233:14: error: too many arguments to function 'acbp->callback'; expected 0, have 3
 1233 |             (*acbp->callback)(acbp->userdata, PortWWN, eventType);
      |             ~^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~
hbaapilib.c:202:27: note: declared here
  202 |     void                (*callback)();
      |                           ^~~~~~~~
hbaapilib.c: In function 'HBA_RegisterForAdapterEvents':
hbaapilib.c:1281:20: error: assignment to 'void (*)(void)' from incompatible pointer type 'void (*)(void *, HBA_WWN,  HBA_UINT32)' {aka 'void (*)(void *, struct HBA_wwn,  unsigned int)'} [-Wincompatible-pointer-types]
 1281 |     acbp->callback = callback;
      |                    ^
hbaapilib.c: In function 'adapterportevents_callback':
hbaapilib.c:1319:14: error: too many arguments to function 'acbp->callback'; expected 0, have 4
 1319 |             (*acbp->callback)(acbp->userdata, PortWWN, eventType, fabricPortID);
      |             ~^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~
hbaapilib.c:202:27: note: declared here
  202 |     void                (*callback)();
      |                           ^~~~~~~~
hbaapilib.c: In function 'HBA_RegisterForAdapterPortEvents':
hbaapilib.c:1372:20: error: assignment to 'void (*)(void)' from incompatible pointer type 'void (*)(void *, HBA_WWN,  HBA_UINT32,  HBA_UINT32)' {aka 'void (*)(void *, struct HBA_wwn,  unsigned int,  unsigned int)'} [-Wincompatible-pointer-types]
 1372 |     acbp->callback = callback;
      |                    ^
hbaapilib.c: In function 'adapterportstatevents_callback':
hbaapilib.c:1409:14: error: too many arguments to function 'acbp->callback'; expected 0, have 3
 1409 |             (*acbp->callback)(acbp->userdata, PortWWN, eventType);
      |             ~^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~
hbaapilib.c:202:27: note: declared here
  202 |     void                (*callback)();
      |                           ^~~~~~~~
hbaapilib.c: In function 'HBA_RegisterForAdapterPortStatEvents':
hbaapilib.c:1462:20: error: assignment to 'void (*)(void)' from incompatible pointer type 'void (*)(void *, HBA_WWN,  HBA_UINT32)' {aka 'void (*)(void *, struct HBA_wwn,  unsigned int)'} [-Wincompatible-pointer-types]
 1462 |     acbp->callback = callback;
      |                    ^
hbaapilib.c: In function 'targetevents_callback':
hbaapilib.c:1502:14: error: too many arguments to function 'acbp->callback'; expected 0, have 4
 1502 |             (*acbp->callback)(acbp->userdata, hbaPortWWN,
      |             ~^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~
hbaapilib.c:202:27: note: declared here
  202 |     void                (*callback)();
      |                           ^~~~~~~~
hbaapilib.c: In function 'HBA_RegisterForTargetEvents':
hbaapilib.c:1557:20: error: assignment to 'void (*)(void)' from incompatible pointer type 'void (*)(void *, HBA_WWN,  HBA_WWN,  HBA_UINT32)' {aka 'void (*)(void *, struct HBA_wwn,  struct HBA_wwn,  unsigned int)'} [-Wincompatible-pointer-types]
 1557 |     acbp->callback = callback;
      |                    ^
hbaapilib.c: In function 'linkevents_callback':
hbaapilib.c:1598:14: error: too many arguments to function 'acbp->callback'; expected 0, have 5
 1598 |             (*acbp->callback)(acbp->userdata, adapterWWN,
      |             ~^~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~
hbaapilib.c:202:27: note: declared here
  202 |     void                (*callback)();
      |                           ^~~~~~~~
hbaapilib.c: In function 'HBA_RegisterForLinkEvents':
hbaapilib.c:1650:20: error: assignment to 'void (*)(void)' from incompatible pointer type 'void (*)(void *, HBA_WWN,  HBA_UINT32,  void *, HBA_UINT32)' {aka 'void (*)(void *, struct HBA_wwn,  unsigned int,  void *, unsigned int)'} [-Wincompatible-pointer-types]
 1650 |     acbp->callback = callback;
      |                    ^
make[1]: *** [Makefile:470: hbaapilib.lo] Error 1
make[1]: Leaving directory '/build/reproducible-path/libhbaapi-2.2.9'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: libhbaapi
Source-Version: 2.2.9-5
Done: Santiago Vila <sanvila@debian.org>

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

Debian distribution maintenance software
pp.
Santiago Vila <sanvila@debian.org> (supplier of updated libhbaapi 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: Sun, 07 Dec 2025 10:20:00 +0100
Source: libhbaapi
Architecture: source
Version: 2.2.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Santiago Vila <sanvila@debian.org>
Closes: 951868 1045787 1097193
Changes:
 libhbaapi (2.2.9-5) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Helmut Grohne ]
   * Move HBAAPI.pc to a multiarch location. Closes: #951868.
 .
   [ Santiago Vila ]
   * Build using C17 standard with GNU extensions. Closes: #1097193.
   * Fix clean target. Closes: #1045787.
   * d/control: Drop "Rules-Requires-Root: no" (default).
   * d/control: Drop "Priority: optional" (default).
   * d/control: Update standards-version.
   * Add debian/salsa-ci.yml.
Checksums-Sha1:
 30b0c2ba826ffa5b97a19cd513e10fbd38a1301e 1556 libhbaapi_2.2.9-5.dsc
 bb42b20b965bfbc8dce143b920b8d0e8b327433a 40944 libhbaapi_2.2.9-5.debian.tar.xz
 e655583d94430e1424eb038e11dc602fa4321da8 5053 libhbaapi_2.2.9-5_source.buildinfo
Checksums-Sha256:
 290ee4082423a57c7f6cba45f8fdb2fa29ea1a5f206e7c4970c52bc95ca7ce08 1556 libhbaapi_2.2.9-5.dsc
 78010e0ab7655574b209835e7f4d77f8b034d01fce4ecdd33287813fac99b066 40944 libhbaapi_2.2.9-5.debian.tar.xz
 77eb0dadc45f0f67f6bf233da2915bef5c45ed5efa0b79f9a4aadae9d6967d68 5053 libhbaapi_2.2.9-5_source.buildinfo
Files:
 e6a69ddeb843368ce4f5df7302a5b023 1556 libs optional libhbaapi_2.2.9-5.dsc
 10635fbbcec3883f19470f2e15f21580 40944 libs optional libhbaapi_2.2.9-5.debian.tar.xz
 16823eaaae01690ce9c270624ef3086d 5053 libs optional libhbaapi_2.2.9-5_source.buildinfo

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

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmk1UMUACgkQQc5/C58b
izKmjQgAiTvQ9p18x2eFIS0t1oGZGDkmJLxySk8/2cRJhWnYE0hUN4LjxMYBwgoA
xcG6B8HkXld3SjTEdl7nI6yiIOlYg4cNL1ktCnCdUrRyoQzQejB5vzqbhv7JDDqM
9ATEfLkINXEk6MJqGq/VnWDElJqs0WFEwNmIbfeYp+BNBkQGy6pVCufv7ski5fCp
kGdHDH5wZqn3OL1pxhlCnYYSlUL9Ip0D4c0aMTtDcNbD/9btJi5Obn3QFWYk5Aib
/WNFiHsMKLkC7D5AyqegBUIHkl9qNtasbn37BxIlwan58T+j4Xuk7zcinDKX4isX
/k737ca0clCQT0h1HTtGaMukP7FFSQ==
=oq1q
-----END PGP SIGNATURE-----

Attachment: pgpeONU0oIdVs.pgp
Description: PGP signature


--- End Message ---
Reply to: