the current ebuild passes --without-context to the build (presumably because it's been ported to very few arches). but that doesn't actually disable building of the code because the coroutines module also uses the context module. it does mean the headers don't get installed, but that's it. i guess the ebuild should also pass along --without-coroutines see upstream URL for more details
Well, some things. 1) --without-context does not disable headers installing, they are removed later in src_install in ebuild; 2) fixes for different boost version(from 1.53 to 1.55) that i have implemented are differs, because of differencies in buildsystem. Quick testing reveals no breakages, but some deeper shit can be possible, so, sorry about that - and file a bug if this will happen. + 27 Dec 2013; Sergey Popov <pinkbyte@gentoo.org> -boost-1.53.0.ebuild, + +boost-1.53.0-r1.ebuild, -boost-1.54.0.ebuild, +boost-1.54.0-r1.ebuild: + Properly disable all code, which depends on Boost.Context and remove all + redundant headers, wrt bug #493116. Thanks to Mike Frysinger for discovering + this issue. Drop old revisions + 27 Dec 2013; Sergey Popov <pinkbyte@gentoo.org> -boost-1.55.0.ebuild, + +boost-1.55.0-r1.ebuild, metadata.xml: + Revision bump: implement conditional building of Boost.Context library via + 'context' USE-flag. Drop old revision
