http://www.boost.org/users/history/version_1_58_0.html Reproducible: Always
emerge --info and build log? Not a duplicate of: 546882?
(In reply to Barnaby from comment #1) > emerge --info and build log? Not a duplicate of: 546882? Barnaby, I'm not sure why either of those would be required for a version bump request... Regarding 546822, the two are related, but not duplicates as far as I can tell. I'm just going to mark it as a "See also". C++ team, obv feel free to change it as necessary.
I am working on this, no estimations however :-/
I have just manually added a local ebuild file to build boost-1.58 (I copied the boost-1.57 file and renamed it to boost-1.5.8 and removed the "${FILESDIR}/${PN}-1.55.0-tools-c98-compat.patch" patch from the ebuild) and was now finally able to build boost with gcc-5.1. Previous to this I wasn't able to build any earlier boost version. After this update I was then subsequently able to build Icinga-2.3.5, which also didn't build against boost-1.5.6/gcc-5.1 combination I had installed previously. So in my case upgrading to boost-1.58 fixed real build problems I was seeing. I hope it is in the official tree real soon.
+*boost-build-1.58.0 (13 Jul 2015) + + 13 Jul 2015; Sergey Popov <pinkbyte@gentoo.org> +boost-build-1.58.0.ebuild: + Version bump, wrt bug #549138 +*boost-1.58.0 (13 Jul 2015) + + 13 Jul 2015; Sergey Popov <pinkbyte@gentoo.org> +boost-1.58.0.ebuild: + Version bump, wrt bug #549138 In tree, hardmasked as usual
Could you, please, apply patches for the known issues in this boost version, which are listed at http://www.boost.org/users/history/version_1_58_0.html? At least the one for python 3.3?
+*boost-1.58.0-r1 (27 Jul 2015) + + 27 Jul 2015; Sergey Popov <pinkbyte@gentoo.org> -boost-1.58.0.ebuild, + +boost-1.58.0-r1.ebuild, + +files/boost-1.58.0-fix-non-constexpr-types-regression.patch: + Revision bump: backport upstream patch, that fixes regression in + Boost.Fusion, drop python 3.3 support. Drop old revision Thanks, added. Unfortunately python patch that are provided on upstream 1.58 version page is not enough to fix this, so i dropped 3.3 support entirely
