from /var/tmp/portage/net-libs/srt-1.4.2/work/srt-1.4.2/srtcore/api.cpp:64: /var/tmp/portage/net-libs/srt-1.4.2/work/srt-1.4.2/srtcore/sync.h: In static member function ‘static constexpr srt::sync::TimePoint<Clock> srt::sync::TimePoint<Clock>::min()’: /var/tmp/portage/net-libs/srt-1.4.2/work/srt-1.4.2/srtcore/sync.h:182:68: error: ‘numeric_limits’ was not declared in this scope 182 | static inline ATR_CONSTEXPR TimePoint min() { return TimePoint(numeric_limits<uint64_t>::min()); } | ^~~~~~~~~~~~~~ /var/tmp/portage/net-libs/srt-1.4.2/work/srt-1.4.2/srtcore/sync.h:182:94: error: ‘::min’ has not been declared; did you mean ‘std::min’? 182 | static inline ATR_CONSTEXPR TimePoint min() { return TimePoint(numeric_limits<uint64_t>::min()); } ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no-multilib-20210423-202814 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.1 [3] x86_64-pc-linux-gnu-11.1.0 * clang version 12.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/12/bin /usr/lib/llvm/12 12.0.0 Python 3.8.9 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.51.0 * The Glorious Glasgow Haskell Compilation System, version 8.10.4 [1] php7.3 * [2] php7.4 [3] php8.0 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Mon May 3 13:05:13 UTC 2021 emerge -qpvO net-libs/srt [ebuild N ] net-libs/srt-1.4.2 USE="-gnutls"
Created attachment 705738 [details] emerge-info.txt
Created attachment 705741 [details] emerge-history.txt
Created attachment 705744 [details] environment
Created attachment 705747 [details] etc.portage.tar.bz2
Created attachment 705750 [details] logs.tar.bz2
Created attachment 705753 [details] net-libs:srt-1.4.2:20210503-134105.log
Created attachment 705756 [details] temp.tar.bz2
patch from Bug #787023 fixes this
*** This bug has been marked as a duplicate of bug 787023 ***