[Debian-med-packaging] Bug#997199: libmaus2: FTBFS: ./libmaus2/avl/AVLSet.hpp:55:66: error: ‘numeric_limits’ is not a member of ‘std’
Lucas Nussbaum
lucas at debian.org
Sat Oct 23 20:13:37 BST 2021
Source: libmaus2
Version: 2.0.803+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall -Wnon-virtual-dtor -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++17 -pthread -fopenmp -c -o test/testavlset-testavlset.o `test -f 'test/testavlset.cpp' || echo './'`test/testavlset.cpp
> In file included from test/testavlset.cpp:20:
> ./libmaus2/avl/AVLSet.hpp:55:66: error: ‘numeric_limits’ is not a member of ‘std’
> 55 | static index_type const nullindex = std::numeric_limits<index_type>::max();
> | ^~~~~~~~~~~~~~
> ./libmaus2/avl/AVLSet.hpp:55:91: error: expected primary-expression before ‘>’ token
> 55 | static index_type const nullindex = std::numeric_limits<index_type>::max();
> | ^
> ./libmaus2/avl/AVLSet.hpp:55:94: error: ‘::max’ has not been declared; did you mean ‘std::max’?
> 55 | static index_type const nullindex = std::numeric_limits<index_type>::max();
> | ^~~
> | std::max
> In file included from /usr/include/c++/11/algorithm:62,
> from test/testavlset.cpp:19:
> /usr/include/c++/11/bits/stl_algo.h:3467:5: note: ‘std::max’ declared here
> 3467 | max(initializer_list<_Tp> __l, _Compare __comp)
> | ^~~
> make[3]: *** [Makefile:10232: test/testavlset-testavlset.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libmaus2_2.0.803+dfsg-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
More information about the Debian-med-packaging
mailing list