This bug is used for the tracking of packages broken by the upcoming GCC 4.7,
which has now entered the stage 3.
- File a NEW bug for each issue and make it BLOCK this one. Assign these bugs
to the maintainer of the package in question, NOT firstname.lastname@example.org please.
- Bugs filed without patches will be closed as INVALID.
- Don't use this bug for issues in GCC 4.6 itself. File a new bug and assign
it to the toolchain team.
- Please keep this tracker free from comments. Discussion should take place
on the relevant bugs.
With previous versions of gcc, there was a (masked) ebuild in the main portage tree so that we could install it for tests... but there's no 4.7 ebuild in current tree. Why is it different than before ? Is the ebuild in some overlay ?
I'm working on it, but I don't have a lot of time these days. Follow along in bug #409315.
There's also a git ebuild in the toolchain overlay.