It seems that the GCC upgrade page (http://www.gentoo.org/doc/en/gcc-upgrading.xml) has an error. Trying to upgrade gcc myself, after a stage3 installation, I noticed a strange difference between 2 sections (section 3 and 4). The 4. section (upgrading GCC on first install), explains to use twice the "emerge -uav", when using the "emerge -e system" procedure. If i compare that with the 3. section (from gcc-3.3 to gcc-3.4), emerge -uav i used only once, and after we should run emerge -e system. Secondarly, on the 4. section, the last command isnt logical: the page doestn explains how to unmerge the old version of GCC but the new one: "emerge -aC "<sys-devel/gcc-YOUR-NEW-GCC-VERSION""
(In reply to comment #0) > The 4. section (upgrading GCC on first install), explains to use twice the > "emerge -uav", when using the "emerge -e system" procedure. If i compare that > with the 3. section (from gcc-3.3 to gcc-3.4), emerge -uav i used only once, > and after we should run emerge -e system. It doesn't say to to run "emerge -uav" twice. Both upgrades describe 2 ways, you pick one and ignore the other. > Secondarly, on the 4. section, the last command isnt logical: the page doestn > explains how to unmerge the old version of GCC but the new one: "emerge -aC > "<sys-devel/gcc-YOUR-NEW-GCC-VERSION"" That removes the previous version of gcc, just like it says. Note the '<'.
Forgot to mention you might find http://www.gentoo.org/doc/fr/gcc-upgrading.xml less confusing :)
>> Secondarly, on the 4. section, the last command isnt logical: the page doestn >> explains how to unmerge the old version of GCC but the new one: "emerge -aC >> "<sys-devel/gcc-YOUR-NEW-GCC-VERSION"" > >That removes the previous version of gcc, just like it says. Note the '<'. Oups really sorry ... I did read it to fast :) >> The 4. section (upgrading GCC on first install), explains to use twice the >> "emerge -uav", when using the "emerge -e system" procedure. If i compare that >> with the 3. section (from gcc-3.3 to gcc-3.4), emerge -uav i used only once, >> and after we should run emerge -e system. > >It doesn't say to to run "emerge -uav" twice. Both upgrades describe 2 ways, >you pick one and ignore the other. If you try to make _exactly_ as described, on the 4. section, "emerge -e system procedure", somebody could easely make it twice; probably because the title "Using revdep-rebuild" is to low, and should be before the "Code listing 4.1" code ...
