Maintainers, please check if =sys-devel/gcc-4.6.4 can go stable and CC arches.
Ping. This is blocker a security bug for more than 3 months.
Any problem with CCing arches in a week?
Yeah, go ahead. Though I really don't see how gcc-4.6.4 is a dependency of freetype.
This? 24 Dec 2013; Ryan Hill <dirtyepic@gentoo.org> gcc-4.6.4.ebuild, gcc-4.7.3-r1.ebuild: 4.6.4 p1.1: Fix ICE with -fprefetch-loop-arrays (bug #454568) and fix gcj build with new freetype (bug #494606). 4.7.3 p1.4: Fix gcj build with new freetype (bug #494606). 23 Dec 2013; Ryan Hill <dirtyepic@gentoo.org> gcc-4.6.0.ebuild, gcc-4.6.1-r1.ebuild, gcc-4.6.2.ebuild, gcc-4.6.3.ebuild, gcc-4.6.4.ebuild, gcc-4.7.0.ebuild, gcc-4.7.1.ebuild, gcc-4.7.2-r1.ebuild, gcc-4.7.3-r1.ebuild, gcc-4.8.0.ebuild, gcc-4.8.1-r1.ebuild, gcc-4.8.2.ebuild, metadata.xml: 4.8.2 p1.1: Fix segfault with std::nth_element (bug #494796) and build failures in gcj due to freetype include dir changes (bug #494606). Rename gtk USE flag to awt. Remove lto USE flag - lto support is now always available. Remove messages.
Yep.
Stable for HPPA.
x86 stable
arm stable
and64 stable
Just so this is on the record somewhere. arm64 compiler minimum is 4.8.2 and I plan to be aggressively get onto 4.9 as arch bring up starts to wind down.
ia64 stable, sparc will pass since 4.6 didn't work fine there.
ppc64 stable