I have recently unmasked glibc-2.16 and gcc-4.7.1. In the process I had to unmask dev-libs/boost:1.50 and dev-util/boost-build:1.50 as well.
Shortly after dev-util/boost-build-1.50.0-r1 was released, and it failed to build and subsequently -r2 and -r3 failed with identical errors.
Now dev-libs/boost-1.50.0-r1 depends on the -r3 version, which doesn't build on my system.
Does anybody else see this problem? or have an idea as to what's going on?

Last edited by Leo Laursen on Fri Aug 24, 2012 1:05 pm; edited 1 time in total

Yes, I have successfully done a emerge -e world, and resolved all issues, except x11-base/xorg-server-1.12.99.904, which does compile with gcc-4.6.3, and this.
Also I have been running the unstable branch of Gentoo for about 10 years, so it is not the first time I have upgraded the toolchain.
The fact is that dev-util/boost-build-1.50.0 is OK, but the later releases, which supposedly should fix some Python issues, breaks it on my system.
I guess I'll have to use trial and error to see if my crazy optimization conflicts with the changes in the latest releases.

Actually Boost 1.50 was the only version that compiled with glibc-2.16, and it was that bug report that gave me the idea to unmask it.
Obviously our interpretation differs. The way I understand it, you have to use boost-1.50 with glibc-2.16, and it works; except for the last 3 releases.

I tried with -python and without -march=native and with the standard tilded version of make--3.82-r4 but with no success.
I also tried without any portage features (ccache ...) and with only one job (make and emerge) with no success either.

I have never been able to emerge >=boost-build-1.50.0

Any ideas ?

EDIT : I just remerge gcc libtool and ghc, and I still got the same problem.