| 1 |
Jarry schrieb am 30.03.2009 19:56: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> today after syncing I found new version of GCC being available, |
| 5 |
> "emerge --pretend --update --deep --newuse world" shows: |
| 6 |
> |
| 7 |
> [ebuild NS ] sys-devel/gcc-4.3.2-r3 [4.1.2] USE="..." |
| 8 |
> |
| 9 |
> I found a "Gentoo GCC Upgrade Guide", but it deals with GCC 3.x, |
| 10 |
> or 3.x->4.x. Should I follow that guide when upgrading 4.x version |
| 11 |
> of GCC too? In a summary, the upgrade guide recommends this way: |
| 12 |
> |
| 13 |
> # emerge -uav gcc |
| 14 |
> # gcc-config x86_64-pc-linux-gnu-4.3.2-r3 |
| 15 |
> # env-update && source /etc/profile |
| 16 |
> # emerge --oneshot -av libtool |
| 17 |
> # emerge -eav system |
| 18 |
> # emerge -eav world |
| 19 |
> # emerge -aC =sys-devel/gcc-4.1.2 |
| 20 |
> |
| 21 |
> I'm asking just to be sure, because I have such a bad feeling, |
| 22 |
> that screwing up gcc upgrade might render my system unusable... |
| 23 |
> |
| 24 |
> Jarry |
| 25 |
> |
| 26 |
> |
| 27 |
|
| 28 |
The recommendations in the section "General Upgrade Instructions" should |
| 29 |
apply here. |
| 30 |
|
| 31 |
Another thing probably worth to mention is that some big packages (xorg, |
| 32 |
mono, firefox, etc) are about to go stable in the near future. So it is |
| 33 |
maybe a good idea to upgrade this packages in one go with the gcc |
| 34 |
upgrade to avoid needlessly double compilation. |
| 35 |
|
| 36 |
-- |
| 37 |
Daniel Pielmeier |
Archives