why the hell would you emerge -e world? it's not worth it...wing wrote:Yup, released yesterday. Well, I'm gonna see if I can bootstrap this one (with FSF Binutils-2.16 and glibc-2.3.5), I'm compiling it now, then I'm gonna do an emerge -e world.
If I did multiple emerge -e world on gcc-4.0.1 and glibc-2.3.6 snapshots, I can certainly do them on this one. 'sides, my machine is fast enough to only take around a day or so to do ~500 packages.G2k wrote:why the hell would you emerge -e world? it's not worth it...wing wrote:Yup, released yesterday. Well, I'm gonna see if I can bootstrap this one (with FSF Binutils-2.16 and glibc-2.3.5), I'm compiling it now, then I'm gonna do an emerge -e world.
I don't claim to understand the ebuild system which may stuff this process up, but when gcc is built it rebuilds itself with itself and that is the final binary... ie gcc 3.4.3 when built with any other gcc ends up building itself again with gcc 3.4.3..Arainach wrote:Switching from plain 3.4.3-r1 to 3.4.3-r1 built with 3.4.3-r1 reduced my compile times by an additional 10-25% on huge ebuilds (like the toolkit).
are you sure that's not ccache? that's a ridiculous amount of improvement.Arainach wrote:Switching from plain 3.4.3-r1 to 3.4.3-r1 built with 3.4.3-r1 reduced my compile times by an additional 10-25% on huge ebuilds (like the toolkit).
gcc builds in three stages. it builds itself with the system compiler, then uses that compiler to build itself again with profile-generation, then uses that profile information to build the final compiler (make profiledbootstrap). the currently popular idea is that in the first part, the new compiler built with the old won't be as "advanced" as if it was the new being built with the new, so the general philosophy is to build it twice. whether this has any affect or not i don't know, but if it does it's probably pretty small. i used to believe it but now i'm actually not that convinced it's any better - especially these days where later versions are proving to be worse performers.I don't claim to understand the ebuild system which may stuff this process up, but when gcc is built it rebuilds itself with itself and that is the final binary... ie gcc 3.4.3 when built with any other gcc ends up building itself again with gcc 3.4.3..

Yes a lot, check the list on gcc.gnu.org. But it also deprecates several patches.StringCheesian wrote:Does 3.4.4 fix any bugs that the 3.4.3 ebuild doesn't already apply patches for?
There's a Gentoo bugzilla entry for 3.4.4, but it seems to have been ignored... What could be taking so long?
Code: Select all
media-libs/faad2-2.0-r6
media-libs/faac-1.24
media-plugins/gst-plugins-faac-0.8.8
Code: Select all
# Unmask every gcc version less than 4:
<sys-devel/gcc-4 -*I doStringCheesian wrote: I don't see why it's masked...
