Bug 439182 – dev-db/mongodb-2.2.0-r1 BOOST_FILESYSTEM_VERSION 3 support (>dev-libs/boost-1.45)

• Status: RESOLVED DUPLICATE of bug 425190
• Product: Gentoo Linux

[Description Andrew Aladjev 2012-10-21 16:38:47 UTC]

I've tried to install mongodb for our new rails project, but latest ebuild mongodb-2.2.0-r1 suddenly supports only <dev-libs/boost-1.49

But boost-1.49 cannot be build with glibc 2.16.0 (this was fixed in boost-1.51). Boost-1.51 have only BOOST_FILESYSTEM_VERSION 3, but mongodb used version 2

I've created very simple patch according to:
1. automatic name portability error detection was dropped
we dont need to write:
#if( BOOST_VERSION >= 104500 )
    boost::filesystem::path::default_name_check( boost::filesystem2::no_check );
#else
    boost::filesystem::path::default_name_check( boost::filesystem::no_check );
#endif
2. native_directory_string() -> string()
3. native_file_string() -> string()

info:
http://www.boost.org/doc/libs/1_45_0/libs/filesystem/v3/doc/faq.htm and http://www.boost.org/doc/libs/1_45_0/libs/filesystem/v3/doc/deprecated.html

Reproducible: Always

[Comment 1 Andrew Aladjev 2012-10-21 16:40:41 UTC]

Created attachment 327086 [details]
boost_filesystem_3.patch

[Comment 2 Andrew Aladjev 2012-10-21 17:00:40 UTC]

PS I've used boost-1.51 from poly-c overlay

[Comment 3 Johan Bergström 2012-10-22 21:43:22 UTC]

This is fixed upstream as of https://jira.mongodb.org/browse/SERVER-4314 - which availability seems to be 2.3.0. I'm not sure we should start patching $src based on out-of-x86-ebuilds just yet. If boost 1.51 lands before 2.3.0 arrives, we could merge this: https://github.com/mongodb/mongo/commit/b3b1949de30b5dc1bde3d91aa197a8587d17d193

...but I would at least prefer avoiding these kind of patches in between upstream releases.

[Comment 4 Johan Bergström 2012-10-22 21:45:00 UTC]

Actually, it seems that filesystem v2 support was rid of in boost 1.50, which is masked in tree.

[Comment 5 Diego Elio Pettenò (RETIRED) 2012-10-31 16:35:20 UTC]

Wait, I thought they fixed this with 2.2 already, damn it.

Anyway, you'd better apply the patch now since boost-1.51.0-r1 is going to be unmasked next week with glibc-2.16.

[Comment 6 Diego Elio Pettenò (RETIRED) 2012-10-31 18:48:06 UTC]

*** This bug has been marked as a duplicate of bug 425190 ***