The wesnoth ebuild has this in RDEPEND : "|| ( dev-libs/boost:1.42 dev-libs/boost:1.41 dev-libs/boost:1.35 )" But boost-1.35 is actually slot 0, not slot 1.35 : "|| ( dev-libs/boost:1.42 dev-libs/boost:1.41 dev-libs/boost:0 )" I've changed my local ebuild and verified that it works with slot 0. Thanks to tomboy64 and Tommy[D] in #gentoo-dev-help for helping me figure this one out :) Reproducible: Always Work around for the meanwhile, if anyone needs it: unmask =dev-libs/boost-1.41.0 or =dev-libs/boost-1.42.0 and build wesnoth against one of those.
could u attache this local ebuild plz, i have the same problem: http://bugs.gentoo.org/show_bug.cgi?id=311369 thanks
Created attachment 225463 [details] requested by tman
whoops. Should be fixed up now.
Now it exclusively wants the only boost version that is slotted :0 sabayon ~ # emerge -av games-strategy/wesnoth * IMPORTANT: 6 news items need reading for repository 'gentoo'. * Use eselect news to read news items. These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild NS ] dev-util/boost-build-1.35.0-r2 [1.37.0, 1.39.0, 1.41.0] USE="python -examples" 22,868 kB [ebuild NS ] dev-libs/boost-1.35.0-r5 [1.39.0, 1.41.0-r2] USE="eselect python -doc -expat -icu -mpi -test -tools" 6 kB [ebuild U ] games-strategy/wesnoth-1.8 [1.6.5] USE="dbus%* nls -dedicated -doc% -server -tinygui" 0 kB Total: 3 packages (1 upgrade, 2 in new slots), Size of downloads: 22,874 kB
Confirmed. I think it should be >=dev-libs/boost-1.35 instead of >=dev-libs/boost-1.35:0 I tested it that way, with success. "# how do I hate boost? Let me count the ways..." :)
No, I'm only support the slotted ebuilds. upgrade your boost version.
(In reply to comment #6) > No, I'm only support the slotted ebuilds. upgrade your boost version. > Huh? I am using the latest stable boost, in the 1.41 slot, and it looks like Joost has that as well. Your ebuild depends exclusively on the 0 slot, which is 1.35.
Oh, the summary is very misleading.
ok, fixed that up. Thanks.