[Debian-med-packaging] Bug#1013026: quorum: ftbfs with GCC-12

[Matthias Klose]

Package: src:quorum
Version: 1.1.1-6
Severity: normal
Tags: sid bookworm
User: debian-gcc at lists.debian.org
Usertags: ftbfs-gcc-12

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/quorum_1.1.1-6_unstable_gcc12.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
checking dependency style of g++... none
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for pthread_create in -lpthread... yes
checking for clock_gettime in -lrt... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for yaggo... /usr/bin/yaggo
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for jellyfish-2.0... yes
checking for jellyfish... /usr/bin/jellyfish
checking for __int128... yes
checking for g++ options needed to detect all undeclared functions... none needed
checking whether strerror_r is declared... yes
checking whether strerror_r returns char *... yes
checking for _Bool... no
checking for stdbool.h that conforms to C99... yes
checking for size_t... yes
checking for ssize_t... yes
checking for ptrdiff_t... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
   dh_auto_build -O--no-parallel
	make -j1
make[1]: Entering directory '/<<PKGBUILDDIR>>'
yaggo src/error_correct_reads_cmdline.yaggo src/error_correct_reads_cmdline.hpp
/usr/bin/yaggo --license ./header-license -o src/error_correct_reads_cmdline.hpp src/error_correct_reads_cmdline.yaggo
yaggo src/create_database_cmdline.yaggo src/create_database_cmdline.hpp
/usr/bin/yaggo --license ./header-license -o src/create_database_cmdline.hpp src/create_database_cmdline.yaggo
yaggo src/merge_mate_pairs_cmdline.yaggo src/merge_mate_pairs_cmdline.hpp
/usr/bin/yaggo --license ./header-license -o src/merge_mate_pairs_cmdline.hpp src/merge_mate_pairs_cmdline.yaggo
yaggo src/split_mate_pairs_cmdline.yaggo src/split_mate_pairs_cmdline.hpp
/usr/bin/yaggo --license ./header-license -o src/split_mate_pairs_cmdline.hpp src/split_mate_pairs_cmdline.yaggo
make  all-am
make[2]: Entering directory '/<<PKGBUILDDIR>>'
g++ -DHAVE_CONFIG_H -I.  -I./include -I. -I/usr/include/jellyfish-2.3.0 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -g -O2 -std=c++0x -Werror -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -DHAVE_NUMERIC_LIMITS128 -c -o src/error_correct_reads.o src/error_correct_reads.cc
In file included from ./src/error_correct_reads.hpp:13,
                 from src/error_correct_reads.cc:35:
./src/err_log.hpp:42:34: error: ‘template<class _Arg, class _Result> struct std::unary_function’ is deprecated [-Werror=deprecated-declarations]
   42 |   struct greater_than_pos : std::unary_function<entry, bool> {
      |                                  ^~~~~~~~~~~~~~
In file included from /usr/include/c++/12/bits/refwrap.h:39,
                 from /usr/include/c++/12/vector:66,
                 from src/error_correct_reads.cc:19:
/usr/include/c++/12/bits/stl_function.h:117:12: note: declared here
  117 |     struct unary_function
      |            ^~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
make[2]: *** [Makefile:973: src/error_correct_reads.o] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:707: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j1 returned exit code 2
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2