Unpacking and reviewing boost ebuild versions 1.36.0-r1, 1.37.0-r1, 1.39.0 and 1.40.0, it appears none of them propagate the 1.35.0-r5 patch from bug #244834 (attachment #170173 [details, diff]), causing boost itself to build and install, but causing packages building against boost to fail. Please apply that patch to those versions as well - the same patch should be fine for all of them.
Could you please file an upstream bug [1] about this or give me enough information to file such a bug? Preferably with a newer version like 1.41 in my overlay [2]. Make sure to remove the patch from the ebuild. [1] https://svn.boost.org/trac/boost/report [2] git://github.com/few/few-s-gentoo-overlay.git
Forget about that, it's applied in 1.41.
1.41 isn't in the tree so I can't do anything about that, like test it... I have removed ~hppa keywording from all affected ebuilds now. I will readd them where appropriate when this bug is fixed.
I have 1.41 is in my overlay [1]. The other ebuilds there have it applied too. [1] git://github.com/few/few-s-gentoo-overlay.git
Btw, the "forget about that" was for the upstream bug I asked in comment 1 for. You might get compile failures moaning about --long-double with my 1.41 ebuild. In this case comment-in the --long-double lines in the ebuild (and say that it was needed).
(In reply to comment #3) > 1.41 isn't in the tree so I can't do anything about that, like test it... > > I have removed ~hppa keywording from all affected ebuilds now. I will readd > them where appropriate when this bug is fixed. > This broke some depends. Can you please temporarily remove the keywords, or I will if you want, from these ebuilds until this is all sorted out: media-gfx/exiv2/exiv2-0.18.1-r1.ebuild: ~hppa(default/linux/hppa/10.0) ['>=dev-libs/boost-1.37'] media-gfx/povray/povray-3.7.0_beta32.ebuild: ~hppa(default/linux/hppa/10.0) ['>=dev-libs/boost-1.36'] media-libs/exempi/exempi-2.1.0.ebuild: ~hppa(default/linux/hppa/10.0) ['>=dev-libs/boost-1.37.0']
(In reply to comment #6) > (In reply to comment #3) > > 1.41 isn't in the tree so I can't do anything about that, like test it... > > > > I have removed ~hppa keywording from all affected ebuilds now. I will readd > > them where appropriate when this bug is fixed. > > > > This broke some depends. Can you please temporarily remove the keywords, or I > will if you want, from these ebuilds until this is all sorted out: > > media-gfx/exiv2/exiv2-0.18.1-r1.ebuild: ~hppa(default/linux/hppa/10.0) > ['>=dev-libs/boost-1.37'] > media-gfx/povray/povray-3.7.0_beta32.ebuild: ~hppa(default/linux/hppa/10.0) > ['>=dev-libs/boost-1.36'] > media-libs/exempi/exempi-2.1.0.ebuild: ~hppa(default/linux/hppa/10.0) > ['>=dev-libs/boost-1.37.0'] This bug would be best fixed by simply patching the affected ebuilds - that is what this bug report is all about. Dropping the keywords on the above packages is no solution because other packages depend on those. I would like the dev-libs/boost maintainers to simply go ahead and fix this or, alternatively, to give me the go ahead to add one line to each of the affected ebuilds.
(In reply to comment #4) > I have 1.41 is in my overlay [1]. The other ebuilds there have it applied too. > > [1] git://github.com/few/few-s-gentoo-overlay.git As I said before - I am not going to do that. Since it isn't in the tree (yet), it has nothing to do with keywording. Besides, newer boost versions apparently always come with new incompatibilities, so patching what works is what we need to do now (or rather, yesterday) instead of trying to keep up with upstream. All I need is an OK.
The patch should have been applied to 1.36 and wasn't needed any longer in 1.37 it seems. Since anything >1.35 didn't compile anyway, there's no longer any need. 1.41 (~hppa) is OK so I guess this bug is fixed.
