[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/libvmod-re2_2.0.0-6_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
[...]
**** v1 vsl| 1009 End c
**** dT 2.163
*** v1 CLI RX 106
**** v1 CLI RX|Message from C-compiler:
**** v1 CLI RX|vgc.c:2446:33: error: two or more data types in declaration specifiers
**** v1 CLI RX| 2446 | VCL_BOOL bool;
**** v1 CLI RX| | ^~~~
**** v1 CLI RX|vgc.c:2446:37: error: declaration does not declare anything [-Werror]
**** v1 CLI RX| 2446 | VCL_BOOL bool;
**** v1 CLI RX| | ^
**** v1 CLI RX|vgc.c:2476:33: error: two or more data types in declaration specifiers
**** v1 CLI RX| 2476 | VCL_BOOL bool;
**** v1 CLI RX| | ^~~~
**** v1 CLI RX|vgc.c:2476:37: error: declaration does not declare anything [-Werror]
**** v1 CLI RX|[3 lines truncated]
**** v1 CLI RX|Running C-compiler failed, exited with 1
**** v1 CLI RX|VCL compilation failed
**** dT 2.173
---- v1 FAIL VCL does not compile
* top RESETTING after ./tests/set_sub.vtc
**** dT 2.174
** s1 Waiting for server (3/-1)
** v1 Wait
**** v1 CLI TX|panic.show
*** v1 CLI RX 300
**** v1 CLI RX|Child has not panicked or panic has been cleared
*** v1 debug|Info: manager stopping child
*** v1 debug|Debug: Stopping Child
**** dT 2.224
**** v1 vsl| 0 CLI - EOF on CLI connection, worker stops
**** dT 2.274
*** v1 debug|Info: Child (4790) said Child dies
*** v1 debug|Info: Child (4790) ended
*** v1 debug|Debug: Child cleanup complete
*** v1 debug|Info: manager dies
**** dT 2.278
**** v1 STDOUT EOF
**** dT 2.325
** v1 WAIT4 pid=4581 status=0x0000 (user 1.733096 sys 0.068926)
* top TEST ./tests/set_sub.vtc FAILED
# top TEST ./tests/set_sub.vtc FAILED (2.325) exit=2
FAIL tests/set_sub.vtc (exit status: 2)
============================================================================
Testsuite summary for libvmod-re2 2.0.0
============================================================================
# TOTAL: 29
# PASS: 22
# SKIP: 0
# XFAIL: 0
# FAIL: 7
# XPASS: 0
# ERROR: 0
============================================================================
See src/test-suite.log for debugging.
Some test(s) failed. Please report this to varnish-support@uplex.de,
together with the test-suite.log file (gzipped) and your system
information. Thanks.
============================================================================
make[4]: *** [Makefile:905: test-suite.log] Error 1
make[4]: Leaving directory '/build/reproducible-path/libvmod-re2-2.0.0/src'
make[3]: *** [Makefile:1040: check-TESTS] Error 2
make[3]: Leaving directory '/build/reproducible-path/libvmod-re2-2.0.0/src'
make[2]: *** [Makefile:1104: check-am] Error 2
make[2]: Leaving directory '/build/reproducible-path/libvmod-re2-2.0.0/src'
make[1]: *** [Makefile:527: check-recursive] Error 1
make[1]: Leaving directory '/build/reproducible-path/libvmod-re2-2.0.0'
dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
make: *** [debian/rules:11: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2