235 | typedef typename iterator_traits<BiDirValueIt>::reference reference; | ^~~~~~~~~~~~~~~ /usr/include/boost/container/vector.hpp:235:21: error: expected ; at end of member declaration 235 | typedef typename iterator_traits<BiDirValueIt>::reference reference; | ^~~~~~~~~~~~~~~ | ; /usr/include/boost/container/vector.hpp:235:21: error: redeclaration of typedef int boost::container::vector_insert_ordered_cursor<BiDirPosConstIt, BiDirValueIt>::iterator_traits /usr/include/boost/container/vector.hpp:234:21: note: previous declaration typedef int boost::container::vector_insert_ordered_cursor<BiDirPosConstIt, BiDirValueIt>::iterator_traits 234 | typedef typename iterator_traits<BiDirPosConstIt>::value_type size_type; ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_no_multilib_hardened_systemd-20250112-003502 UNMASKED: Requested by sam >=media-video/ffmpeg-7.0 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-14 * clang version 19.1.6 llvm-config: 19.1.6 Python 3.12.8 go version go1.23.4 linux/amd64 Available Ruby profiles: (none found) Available Rust versions: [1] rust-bin-1.71.1 [2] rust-bin-1.77.1 [3] rust-bin-1.81.0 [4] rust-bin-1.84.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.25_p9 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.13_p11 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.5_p11 [openjdk-bin-21] 4) Eclipse Temurin JDK 8.432_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 [4] openjdk-bin-21 system-vm HEAD of ::gentoo commit d082ab626edbd4d03f0e7420a973d68b49ea23a0 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Thu Jan 16 19:03:32 2025 +0000 2025-01-16 19:03:31 UTC emerge -qpvO =dev-games/simgear-2020.3.19 [ebuild N ] dev-games/simgear-2020.3.19 USE="(dns) openmp -debug -gdal -subversion -test" CPU_FLAGS_X86="sse2"
Created attachment 916764 [details] emerge-info.txt
Created attachment 916765 [details] dev-games:simgear-2020.3.19:20250116-201314.log.xz
Created attachment 916766 [details] emerge-history.txt.xz
Created attachment 916767 [details] environment
Created attachment 916768 [details] etc.clang.tar.xz
Created attachment 916769 [details] etc.portage.tar.xz
Created attachment 916770 [details] logs.tar.xz
Created attachment 916771 [details] qlist-info.txt.xz
Created attachment 916772 [details] temp.tar.xz
simgear-2020.3.20_rc1 is also showing the symptom. -std=gnu++17? How to properly include boost? Even the current has the same inclusion scheme...
FYI the exact same issue appears when building FlightGear on Archlinux from AUR (I have a second machine running Arch and just checked). So this is not an Gentoo exclusive issue, this seems to be an upstream issue.
(In reply to Vamp898 from comment #11) > FYI the exact same issue appears when building FlightGear on Archlinux from > AUR (I have a second machine running Arch and just checked). > > So this is not an Gentoo exclusive issue, this seems to be an upstream issue. That gives a hope it will take less time to find a solution.
https://github.com/acxz/flightgear-arch/issues/19
googling ‘BOOST_MOVE_STD_NS_BEG’ led me to https://git.skewed.de/count0/graph-tool/-/issues/799 -> https://git.skewed.de/count0/graph-tool/-/commit/5fa4b6d77b00ceb301573abf9811493e85b8873a. They had a bundled boost workaround or something though. There's also https://github.com/boostorg/container/issues/292 and https://github.com/boostorg/move/issues/59 which mentions simgear.
2024.01.01 have been released, maybe that one already fixes the issue.
(In reply to Vamp898 from comment #15) > 2024.01.01 have been released, maybe that one already fixes the issue. It appears to be a bug in Boost itself AFAICT.
It appears so, yes. I just assumed they might have implemented an workaround for it. But maybe not^^
After applying the patch at https://github.com/boostorg/move/commit/e9ff3ca0952e680871145f454925614d950cef4d to boost-1.87.0, both simgear and flightgear compile for me.
(In reply to Arve Barsnes from comment #18) > After applying the patch at > https://github.com/boostorg/move/commit/ > e9ff3ca0952e680871145f454925614d950cef4d to boost-1.87.0, both simgear and > flightgear compile for me. I confirm, that it fixes the problem on my system as well. It is surprising how other projects are not involved.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=00b9fdc8c51fed27b6b4762af0f7e9dece80fbab commit 00b9fdc8c51fed27b6b4762af0f7e9dece80fbab Author: Sam James <sam@gentoo.org> AuthorDate: 2025-03-07 13:48:19 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-03-07 13:48:19 +0000 dev-libs/boost: fix boost::move regression Closes: https://bugs.gentoo.org/948204 Signed-off-by: Sam James <sam@gentoo.org> dev-libs/boost/boost-1.87.0-r1.ebuild | 345 +++++++++++++++++++++++++++ dev-libs/boost/files/boost-1.87.0-move.patch | 74 ++++++ 2 files changed, 419 insertions(+)
