The ~amd64 keyword is missing, if it was intentional, it works here.
Only drop the keywords from a package if there are significant changes or the new version depends on unkeyworded packages. Otherwise, just make them ~arch. And if you drop the keywords, you MUST file a bug notifying the affected arch teams.
I dropped the keywords by intention. Alex: Thanks for the news. Tester: I know what I have to do. But the arch-teams have to have something to test, compilation only is not enough. I'll commit an updated version of the package tomorrow with a src_test function and ask the arch-teams to test it. And it is p.masked after all.
Ok, got some news. I've added the boost regression tests to src_test. If you want to run it, just do: FEATURES="test" emerge =dev-libs/boost-1.34_pre20060930 But, I'll still not CC the arch-teams, because I wasn't able to completely run the tests myself. It needs roughly 3 GB storage to run completely. I'm currently setting up a machine to test for ~amd64.
I've just committed a new snapshot which has been tested on amd64 as well and therefore keyworded right away.