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

Bug#1096667: marked as done (fwlogwatch: ftbfs with GCC-15)



Your message dated Sat, 11 Oct 2025 11:19:09 +0000
with message-id <E1v7Xcz-009BsQ-1i@fasolo.debian.org>
and subject line Bug#1096667: fixed in fwlogwatch 1.4-6
has caused the Debian Bug report #1096667,
regarding fwlogwatch: 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.)


-- 
1096667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1096667
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:fwlogwatch
Version: 1.4-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/fwlogwatch_1.4-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

[...]
gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/fwlogwatch-1.4=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DHAVE_ZLIB -DHAVE_GETTEXT -pipe -O2 -Wall  -Wdate-time -D_FORTIFY_SOURCE=2  -c -o resolve.o resolve.c
modes.c: In function ‘mode_rt_response’:
modes.c:617:19: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  617 |   signal(SIGTERM, mode_rt_response_terminate);
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~
      |                   |
      |                   void (*)(void)
/usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’
   88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
modes.c:531:6: note: ‘mode_rt_response_terminate’ declared here
  531 | void mode_rt_response_terminate()
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~
modes.c:707:18: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  707 |   signal(SIGHUP, mode_rt_response_reread_conf);
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                  |
      |                  void (*)(void)
/usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’
   88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
modes.c:423:6: note: ‘mode_rt_response_reread_conf’ declared here
  423 | void mode_rt_response_reread_conf()
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~
modes.c:708:19: error: passing argument 2 of ‘signal’ from incompatible pointer type [-Wincompatible-pointer-types]
  708 |   signal(SIGUSR1, mode_rt_response_reopen_log);
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                   |
      |                   void (*)(void)
/usr/include/signal.h:88:57: note: expected ‘__sighandler_t’ {aka ‘void (*)(int)’} but argument is of type ‘void (*)(void)’
   88 | extern __sighandler_t signal (int __sig, __sighandler_t __handler)
      |                                          ~~~~~~~~~~~~~~~^~~~~~~~~
modes.c:454:6: note: ‘mode_rt_response_reopen_log’ declared here
  454 | void mode_rt_response_reopen_log()
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/signal.h:72:16: note: ‘__sighandler_t’ declared here
   72 | typedef void (*__sighandler_t) (int);
      |                ^~~~~~~~~~~~~~
make[1]: *** [<builtin>: modes.o] Error 1
make[1]: *** Waiting for unfinished jobs....
output.c: In function ‘output_timediff’:
output.c:48:3: warning: ‘__builtin_strncat’ output may be truncated copying 3 bytes from a string of length 3 [-Wstringop-truncation]
   48 |   strncat(td, tmp, 3);
      |   ^
resolve.c: In function ‘resolve_address_sync’:
resolve.c:125:34: warning: ‘%s’ directive output may be truncated writing up to 1024 bytes into a region of size 256 [-Wformat-truncation=]
  125 |         snprintf(fqdn, HOSTLEN, "%s", hbuf);
      |                                  ^~   ~~~~
In file included from /usr/include/stdio.h:970,
                 from resolve.c:4:
In function ‘snprintf’,
    inlined from ‘resolve_address_sync’ at resolve.c:125:2:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:68:10: note: ‘__builtin_snprintf’ output between 1 and 1025 bytes into a destination of size 256
   68 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   69 |                                    __glibc_objsize (__s), __fmt,
      |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   70 |                                    __va_arg_pack ());
      |                                    ~~~~~~~~~~~~~~~~~
rm ipfw.c ipfilter.c cisco_ios.c cisco_pix.c netfilter.c netscreen.c ipchains.c
make[1]: Leaving directory '/build/reproducible-path/fwlogwatch-1.4'
dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" 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: fwlogwatch
Source-Version: 1.4-6
Done: Adrian Bunk <bunk@debian.org>

We believe that the bug you reported is fixed in the latest version of
fwlogwatch, 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 1096667@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 fwlogwatch 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, 11 Oct 2025 14:03:02 +0300
Source: fwlogwatch
Architecture: source
Version: 1.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1096667 1106934
Changes:
 fwlogwatch (1.4-6) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS with GCC 15. (Closes: #1096667)
   * Build depend on libcrypt-dev. (Closes: #1106934)
Checksums-Sha1:
 83fa86cab61f8a737af3b54b97c65573278d51d3 1918 fwlogwatch_1.4-6.dsc
 54eb355b10dcea00c3259ac132927c83ed9e3cde 26824 fwlogwatch_1.4-6.debian.tar.xz
Checksums-Sha256:
 848a5d6bec97d0dc9b602cf17da3de2f2d3aef7c933ac54d19a099de280dc92d 1918 fwlogwatch_1.4-6.dsc
 a31e84f78efab37c2117957110a95275f95eeb502079039475cd817cabfc4cde 26824 fwlogwatch_1.4-6.debian.tar.xz
Files:
 33bb92dc392cb237a58d7da5e362b68c 1918 net optional fwlogwatch_1.4-6.dsc
 c10668563413cd4d62d1d520a087c3a5 26824 net optional fwlogwatch_1.4-6.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmjqOl4ACgkQiNJCh6LY
mLH1ig//U0xeceucSW1DDhHF6Fs2wvk2bwDMe+TBtVAAB8r7pRRhKk6XeodHWv05
hsCd46Us6h+oH/yrGth32tmGQ4nJfHJkrRcnOT9WV+elfvMfwljfnYDT4e6LQTSb
r6P7hxSZbtlce5Gj90XXHQzjKpnPIEq0QcP/YIBch+IMksTHlCYOaN/DLpBfN4n9
NSJVR5Ntx7oIF6hTFkiPPly8QoYwtxmgKJVU52QIw98hzD9SWIdi35l6oGJDJCbW
HX5byKdEX87vCT5YkJVa/xpWADtSRFfXFHJ2EZD+Imh+aJHyGXW8kX3lAc5zItu3
EJy6UwfS84oQgf0tXOsMP/bfRB9AAlFFWYTjz3d6F5hzf6R6aWn3zgzc7YrLkqsl
MZjjx+SI1irTt5igdSK2ld8GH6gAaFIEy8Zkp+JG8s++RPnwtJJJQYI5CyrHwgi+
6lcYX1puN9IwWUYqTibpK4D2eEOeIEh4vvn6+E1Z49VbPxFSTWijNg6JTUdEtcby
3cJq4UCcHG8PsKWTYcVAFvcEj2kEjS43LRsFnxFWkVFttxCI0AqORgGHd+/EmKfV
oUktEpq+aWp/m03WWy4JdAoVisCG+jLzfRZWMCr9aMQWFTnJ9LlIDbxYk1D0ml1m
qlQinE1brNsMG3KMH3X+rWyWv8iT+78kzJcbqvlUFtqvjt5j9uI=
=Pw6D
-----END PGP SIGNATURE-----

Attachment: pgpHBAg4jIMvu.pgp
Description: PGP signature


--- End Message ---

Reply to: