GCC migration

[smolloy]

I was just wondering if any of you gentooers had done the migration from GCC3.3 to 3.4??

If so, did you do the fast version or the long version?? Has anyone had any difficulties with the riskier fast version?? Is it really worthwhile recompiling my whole system with the new compiler??

[loft306]

ive done it both ways but without that nice doc so i have mucked it up more ways than you can imagine... :P but it is gentoo and totaly fixable given enough time but i would recomend tha 2nd way it realy is safer but the emerge -e will take a long time (like usually 3 times longer than the origional install)
now off to do it on this box i think

[smolloy]

So the second (longer) method is gonna take the amount of time it took to install everything I have ever emerged multiplied (approx) by three!!?? Does that include the already ridiculously long openoffice compile??

I noticed this result when I did "emerge -s gcc",

*  sys-devel/gcc
      Latest version available: 3.4.4-r1
      Latest version installed: 3.4.4-r1
      Size of downloaded files: 27,834 kB
      Homepage:    http://www.gnu.org/software/gcc/gcc.html
      Description: The GNU Compiler Collection. Includes C/C++, java compilers, pie+ssp extensions, Haj Ten Brugge runtime bounds checking
      License:     GPL-2 LGPL-2.1

It looks like my last emerge world updated gcc, so I guess I really should go ahead and re-compile my entire system.

It sounds like it could take DAYS to complete!!

[Cabhan]

I actually just finished my update. I took the longer method, and it took me about 1.5 days to recompile everything.

That said, I use ccache, so I dunno if that might have helped or not. But yeah...wasn't too bad.

[smolloy]

I've just finished the first part of the long re-compile -- "emerge -e system" -- and that took 6hours15mins!!! As far as I can tell "emerge -e world" recompiles everything that "emerge -e system" does along with about 200 other files.

This is gonna take a looooooong time :sleep:

[St. Joe]

I did a hybrid of the two methods.
First, I did this emerge set:

# emerge --sync && emerge -uav gcc
# gcc-config i686-pc-linux-gnu-3.4.4
# source /etc/profile

Then this emerge:

# emerge gcc binutils glibc

And finally these:

# revdep-rebuild --library libstdc++.so.5 -- -p -v
# revdep-rebuild --library libstdc++.so.5
# emerge --oneshot sys-libs/libstdc++-v3
# emerge -aC =sys-devel/gcc-3.3*

This was done on two gentoo boxes and both were successful.

[jaboua]

As far as I can tell "emerge -e world" recompiles everything that "emerge -e system" does along with about 200 other files.

emerge -e world is waste of time unless you have to recompile everything! For the GCC update I might have done emerge -e world, but for normal system updates, emerge -NuD is enough (only remerge packages which can be upgraded or is changed because of useflags change + deep).

[smolloy]

Yeah, that's what I normally do, but this time it seemed to make sense to recompile everything with the new version of GCC.

It's been running for about 40 hours now and I'm half way through openoffice -- about 10 hours to go......

[dylunio]

It is said that once you have compiled any toolchain items (gcc, binutils, glibc etc), you should do

emerge -e system
emerge -e system
emenge -e world
emerge -e world

to make sure that all the pragrams are campiled with the latest version of the toolchain.

Take note, that I rarly do this, and when I do I tend to be going on heliday or on a trip since I don't want to be here when it's emerging all these programs.

[smolloy]

I did emerge -p system/world first, and world re-compiles all the same stuff as system plus an additional ~200 files, and the toolchain items were amongst the repeats. I thought this should take care of it.

Do you have a link to where it gave that advice??