from build/opt/mongo/base/error_codes.h:36, from src/mongo/base/status.h:35, from src/mongo/bson/bson_validate.h:34, from src/mongo/shell/shell_utils_extended.cpp:43: src/mongo/shell/shell_utils_extended.cpp:397:13: error: 'ofs' was not declared in this scope; did you mean 'ffs'? 397 | ofs); | ^~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome-j4-20220418-180013 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.1 * clang/llvm (if any): /usr/lib/llvm/14 14.0.1 Python 3.9.12 Available Rust versions: [1] rust-1.60.0 * The following VMs are available for generation-2: *) Eclipse Temurin JDK 11.0.14_p9 [openjdk-bin-11] Available Java Virtual Machines: [1] openjdk-bin-11 system-vm php cli: [1] php7.4 * [2] php8.0 HEAD of ::gentoo commit 9894d2d54628bd26d11e92226a086a07b303686d Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Apr 19 10:54:05 2022 +0000 2022-04-19 10:54:03 UTC emerge -qpvO dev-db/mongodb [ebuild N ] dev-db/mongodb-5.0.5 USE="tools -debug -kerberos -lto -mongosh -ssl" CPU_FLAGS_X86="avx"
Created attachment 771896 [details] emerge-info.txt
Created attachment 771899 [details] dev-db:mongodb-5.0.5:20220419-130606.log
Created attachment 771902 [details] emerge-history.txt
Created attachment 771905 [details] environment
Created attachment 771908 [details] etc.portage.tar.bz2
Created attachment 771911 [details] logs.tar.bz2
Created attachment 771914 [details] temp.tar.bz2
Created attachment 785825 [details, diff] Add missing boost headers
I noticed the same error while building 4.4.10. Looks like this is caused by the latest boost update. The latter changed the way how boost/filesystem/fstream.hpp is included. Solution was to include boost/filesystem/fstream.hpp where needed (see attached patch).
(In reply to Holger from comment #9) > I noticed the same error while building 4.4.10. > Looks like this is caused by the latest boost update. The latter changed the > way how boost/filesystem/fstream.hpp is included. > Solution was to include boost/filesystem/fstream.hpp where needed (see > attached patch). Isn't that fixed already in 4.4.10-r1?
*** This bug has been marked as a duplicate of bug 843290 ***