src/mongo/client/command_writer.cpp: In member function ‘virtual void mongo::CommandWriter::write(const mongo::StringData&, const std::vector<mongo::WriteOperation*>&, bool, bool, const mongo::WriteConcern*, mongo::WriteResult*)’: src/mongo/client/command_writer.cpp:68:78: error: ‘next’ is not a member of ‘boost’ const std::vector<WriteOperation*>::const_iterator next = boost::next(batch_iter); ^~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib_libressl_20181110-220243 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] pypy3 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby24 (with Rubygems) [3] ruby25 (with Rubygems) * emerge -qpvO dev-libs/mongo-cxx-driver [ebuild R ] dev-libs/mongo-cxx-driver-1.1.2-r1 USE="libressl ssl -debug -sasl -static-libs"
Created attachment 555560 [details] emerge-info.txt
Created attachment 555562 [details] dev-libs:mongo-cxx-driver-1.1.2-r1:20181118-115540.log
Created attachment 555564 [details] emerge-history.txt
Created attachment 555566 [details] environment
Created attachment 555568 [details] etc.portage.tbz2
Created attachment 555570 [details] logs.tbz2
Created attachment 555572 [details] temp.tbz2
it is a boost bug https://github.com/boostorg/lockfree/commit/12726cda009a855073b9bedbdce57b6ce7763da2.patch
I suggest handling in gentoo on the boost side.
I had closer look at it in dev-libs/mongo-cxx-driver. The package uses boost::next directly: src/mongo/client/wire_protocol_writer.cpp:80 const std::vector<WriteOperation*>::const_iterator next = boost::next(batch_iter); It should include headers that provide boost::next(): https://www.boost.org/doc/libs/1_67_0/libs/fusion/doc/html/fusion/iterator/functions/next.html Namely #include <boost/fusion/iterator/next.hpp> #include <boost/fusion/include/next.hpp> Assigning back to dev-libs/mongo-cxx-driver maintainer.
Created attachment 555840 [details, diff] mongo-cxx-driver-1.1.2-boost-next.patch mongo-cxx-driver-1.1.2-boost-next.patch seems to be enough to fix build failure.
Toralf, does it build fine for you with boost-1.67.0-r1? I think it's a genuine mongo-cxx-driver bug. It still fails for me the same: src/mongo/client/command_writer.cpp:68:78: note: suggested alternative: 'exa' const std::vector<WriteOperation*>::const_iterator next = boost::next(batch_iter); ^~~~ exa
Indeed, it is still not solved - tested it on this image with boost-1.67.0-r1
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a49d1c1409f75c4af9bf5f539bc06c1c7950e03a commit a49d1c1409f75c4af9bf5f539bc06c1c7950e03a Author: Sergei Trofimovich <slyfox@gentoo.org> AuthorDate: 2018-12-01 12:59:21 +0000 Commit: Sergei Trofimovich <slyfox@gentoo.org> CommitDate: 2018-12-01 12:59:39 +0000 dev-libs/mongo-cxx-driver: tweak for boost-167, bug #671422 Reported-by: Toralf Förster Closes: https://bugs.gentoo.org/671422 Package-Manager: Portage-2.3.52, Repoman-2.3.12 Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org> .../files/mongo-cxx-driver-1.1.2-boost-next.patch | 21 +++++++++++++++++++++ .../mongo-cxx-driver-1.1.2-r1.ebuild | 3 ++- 2 files changed, 23 insertions(+), 1 deletion(-)
