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

Bug#1075142: marked as done (libapache2-mod-qos: ftbfs with GCC-14)

Your message dated Mon, 24 Mar 2025 12:19:12 +0000
with message-id <E1twgls-00F6As-Mb@fasolo.debian.org>
and subject line Bug#1075142: fixed in libapache2-mod-qos 11.74-2
has caused the Debian Bug report #1075142,
regarding libapache2-mod-qos: ftbfs with GCC-14
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.)


-- 
1075142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075142
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:libapache2-mod-qos
Version: 11.74-1
Severity: important
Tags: sid trixie
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is 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-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/libapache2-mod-qos_11.74-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

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-14/porting_to.html

[...]
      |                            ^~~~~~~~~~~~~
/usr/share/apr-1.0/build/libtool --no-silent --mode=link --tag=disable-static x86_64-linux-gnu-gcc -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -lpcre2-8 -L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0    -o apache2/mod_qos.la  -lcrypto -rpath /usr/lib/apache2/modules -module -avoid-version    apache2/mod_qos.lo
libtool: link: x86_64-linux-gnu-gcc -shared  -fPIC -DPIC  apache2/.libs/mod_qos.o   -lpcre2-8 -L/usr/lib/x86_64-linux-gnu/libpcre2-8.so.0 -lcrypto  -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now   -Wl,-soname -Wl,mod_qos.so -o apache2/.libs/mod_qos.so
libtool: link: ( cd "apache2/.libs" && rm -f "mod_qos.la" && ln -s "../mod_qos.la" "mod_qos.la" )
dh_auto_build --sourcedirectory=tools
dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use)
	cd tools && make -j1
make[2]: Entering directory '/<<PKGBUILDDIR>>/tools'
make  all-recursive
make[3]: Entering directory '/<<PKGBUILDDIR>>/tools'
Making all in src
make[4]: Entering directory '/<<PKGBUILDDIR>>/tools/src'
gcc -DHAVE_CONFIG_H -I. -I..   -DLINUX -D_REENTRANT -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2  -I/usr/include/libpng16 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection  -I/usr/include/apr-1.0   -I/usr/include/apr-1.0 -I/usr/include -I/usr/lib/include -c -o qsfilter2.o qsfilter2.c
qsfilter2.c: In function ‘main’:
qsfilter2.c:1803:38: error: passing argument 1 of ‘OPENSSL_sk_new’ from incompatible pointer type [-Wincompatible-pointer-types]
 1803 |     STACK_OF(qs_rule_t) *st = sk_new(STACK_qs_cmp);
      |                                      ^~~~~~~~~~~~
      |                                      |
      |                                      int (*)(const char * const*, const char * const*)
In file included from /usr/include/openssl/safestack.h:24,
                 from qsfilter2.c:59:
/usr/include/openssl/stack.h:34:51: note: expected ‘OPENSSL_sk_compfunc’ {aka ‘int (*)(const void *, const void *)’} but argument is of type ‘int (*)(const char * const*, const char * const*)’
   34 | OPENSSL_STACK *OPENSSL_sk_new(OPENSSL_sk_compfunc cmp);
      |                               ~~~~~~~~~~~~~~~~~~~~^~~
qsfilter2.c:1803:31: error: initialization of ‘struct stack_st_qs_rule_t *’ from incompatible pointer type ‘OPENSSL_STACK *’ {aka ‘struct stack_st *’} [-Wincompatible-pointer-types]
 1803 |     STACK_OF(qs_rule_t) *st = sk_new(STACK_qs_cmp);
      |                               ^~~~~~
qsfilter2.c:1811:15: error: passing argument 1 of ‘OPENSSL_sk_push’ from incompatible pointer type [-Wincompatible-pointer-types]
 1811 |       sk_push(st, (char *)r);
      |               ^~
      |               |
      |               struct stack_st_qs_rule_t *
/usr/include/openssl/stack.h:49:36: note: expected ‘OPENSSL_STACK *’ {aka ‘struct stack_st *’} but argument is of type ‘struct stack_st_qs_rule_t *’
   49 | int OPENSSL_sk_push(OPENSSL_STACK *st, const void *data);
      |                     ~~~~~~~~~~~~~~~^~
qsfilter2.c:1813:13: error: passing argument 1 of ‘OPENSSL_sk_sort’ from incompatible pointer type [-Wincompatible-pointer-types]
 1813 |     sk_sort(st);
      |             ^~
      |             |
      |             struct stack_st_qs_rule_t *
/usr/include/openssl/stack.h:57:37: note: expected ‘OPENSSL_STACK *’ {aka ‘struct stack_st *’} but argument is of type ‘struct stack_st_qs_rule_t *’
   57 | void OPENSSL_sk_sort(OPENSSL_STACK *st);
      |                      ~~~~~~~~~~~~~~~^~
qsfilter2.c:1814:16: error: passing argument 1 of ‘OPENSSL_sk_num’ from incompatible pointer type [-Wincompatible-pointer-types]
 1814 |     i = sk_num(st);
      |                ^~
      |                |
      |                struct stack_st_qs_rule_t *
/usr/include/openssl/stack.h:29:20: note: expected ‘const OPENSSL_STACK *’ {aka ‘const struct stack_st *’} but argument is of type ‘struct stack_st_qs_rule_t *’
   29 | int OPENSSL_sk_num(const OPENSSL_STACK *);
      |                    ^~~~~~~~~~~~~~~~~~~~~
qsfilter2.c:1816:33: error: passing argument 1 of ‘OPENSSL_sk_value’ from incompatible pointer type [-Wincompatible-pointer-types]
 1816 |       r = (qs_rule_t *)sk_value(st, i-1);
      |                                 ^~
      |                                 |
      |                                 struct stack_st_qs_rule_t *
/usr/include/openssl/stack.h:30:24: note: expected ‘const OPENSSL_STACK *’ {aka ‘const struct stack_st *’} but argument is of type ‘struct stack_st_qs_rule_t *’
   30 | void *OPENSSL_sk_value(const OPENSSL_STACK *, int);
      |                        ^~~~~~~~~~~~~~~~~~~~~
make[4]: *** [Makefile:542: qsfilter2.o] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/tools/src'
make[3]: *** [Makefile:364: all-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/tools'
make[2]: *** [Makefile:305: all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/tools'
dh_auto_build: error: cd tools && make -j1 returned exit code 2
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 255
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: libapache2-mod-qos
Source-Version: 11.74-2
Done: Daniel Baumann <daniel@debian.org>

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

Debian distribution maintenance software
pp.
Daniel Baumann <daniel@debian.org> (supplier of updated libapache2-mod-qos 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: Mon, 24 Mar 2025 12:45:27 +0100
Source: libapache2-mod-qos
Architecture: source
Version: 11.74-2
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <daniel@debian.org>
Changed-By: Daniel Baumann <daniel@debian.org>
Closes: 931973 1075142
Changes:
 libapache2-mod-qos (11.74-2) sid; urgency=medium
 .
   * New maintainer (Closes: #931973).
   * Building without qsfilter2 and qsrotate, they are removed in later
     upstream version (Closes: #1075142).
Checksums-Sha1:
 b2982077cf8d649ea148650aaa358bd2cf45f41f 1461 libapache2-mod-qos_11.74-2.dsc
 395fe994966294a8f1cc17980fb302f1fd622a70 5720 libapache2-mod-qos_11.74-2.debian.tar.xz
 0f81adac79e49ecc40207e6c59f1258379c873cb 6497 libapache2-mod-qos_11.74-2_amd64.buildinfo
Checksums-Sha256:
 90cee8ee10ebe6fca7c951b3af75336a2f7001384ddb6d7946bcab3ee156a816 1461 libapache2-mod-qos_11.74-2.dsc
 7b3062d00e3c3b66fba283c2aed8bee390a215cae552f091fd9185740c5b502c 5720 libapache2-mod-qos_11.74-2.debian.tar.xz
 16506671f9c29a5cdd7f7b8c7d921a186aa4e511bb3d1f8b60e7878e9c5372c1 6497 libapache2-mod-qos_11.74-2_amd64.buildinfo
Files:
 f91d78c925eb2e20698d6f3a7ef94397 1461 httpd optional libapache2-mod-qos_11.74-2.dsc
 a607014fe18720bbde51d27830b0b359 5720 httpd optional libapache2-mod-qos_11.74-2.debian.tar.xz
 09f2c0a03744ec6431807d104f92afd3 6497 httpd optional libapache2-mod-qos_11.74-2_amd64.buildinfo


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

iHUEARYKAB0WIQQmmGg4gLaoSj0ERgL7tPDoCoAiLwUCZ+FJ9AAKCRD7tPDoCoAi
L9Q0AQCpW4CYPEhBM+8/v1Y2tKlOdMwhv3wfiqOzjaR7cnvaRwEA7vto0bkzU7I4
1NyrAOoewhtubba5W04ykmP43zcUmAA=
=X7/i
-----END PGP SIGNATURE-----

Attachment: pgpnWw4qtEOuG.pgp
Description: PGP signature


--- End Message ---
Reply to: