This bug will be used to track packages whose stable versions don't work with GCC 4.1.x. In most cases a patch, version bump, or other fix is available in ~arch, and a request will be filed to either backport the fix or stablize a working version.
These arches have GCC 4.1.1 in testing:
amd64, mips, ppc64, s390, x86, x86-fsbd
If you know that any of these arches aren't planning on getting 4.1 stable any time soon make a note.
hppa and ppc already have 4.1.1 stable :p.
All of the packages from 138099 need to go stable for GCC 4.1.1
Also, dev-libs/gmp-4.2.1 and dev-libs/mpfr-2.2.0_p10 will need to go stable...
Well, amd64 and x86 are planning on taking 4.1.1 stable by the 2006.1 release, which isn't that far away.
bug #140905 is not finally fixed, there are still issues with dietlibc and GCC 4.1 on some arches...resolution later.
kind of off topic, but i would _really_ like to see the gcc-4.1.1.ebuild DEPEND on binutils-2.17 which adds support for .weakref[i] and properly handles -msecure-pit on PPC32.
if we really wanted to get crazy, i would say minimum 220.127.116.11.3 for the new --hash-style support[ii] and the MIPS MFTGPR and MTTGPR fixes, but i'm not holding my breath on this one. ;d
that's up to the ppc team if they want to force binutils-2.17
as for the snapshots, not a chance
does the gcc migration doc need to be updated at all?
(In reply to comment #7)
> does the gcc migration doc need to be updated at all?
Don't think so...worked fine here when using the "generic guide".
i just finished working through everything on bug #117482 (except games-*). anything not working on stable should now have a bug here. between the two i think this should pretty much cover it (for x86 at least). :)
Can someone with permission please add a dependency on bug #132667 (qemu not compiling with gcc-4.1.*.
(In reply to comment #10)
> Can someone with permission please add a dependency on bug #132667 (qemu not
> compiling with gcc-4.1.*.
It already blocks the gcc porting bug. This bug here is for stabilisation requests.