| 1 |
There is some really bad directions about how to upgrade to |
| 2 |
gcc 3.2 floating around on forums... Especially: |
| 3 |
|
| 4 |
------------------------------------------------------------ |
| 5 |
http://forums.gentoo.org/viewtopic.php?t=11963 |
| 6 |
GCC 3.2 is here: Now is the time to rebuild everything. How? |
| 7 |
------------------------------------------------------------ |
| 8 |
|
| 9 |
It's 6 pages of mostly wrong information. Anyone following the |
| 10 |
early comments is looking for a headache or complete reinstall. |
| 11 |
|
| 12 |
The first three comments all talk about moving the profile symlink |
| 13 |
and 'emerge -e world' -- Which probably will fail. If you read the |
| 14 |
ENTIRE thing you can find decent info, but none of it is contiguous |
| 15 |
or obvious in the order. |
| 16 |
|
| 17 |
My scripts are up at http://www.gentoo.org/~carpaski/system_update |
| 18 |
and Seemant has 'RoadRunner' on IRC making docs about the process. |
| 19 |
If someone would at least curtail the mis-information, it would |
| 20 |
be beneficial to all parties involved... |
| 21 |
|
| 22 |
Rough Process In Brief: |
| 23 |
1. emerge rsync |
| 24 |
2. emerge portage |
| 25 |
3. emerge rsync |
| 26 |
4. emerge -c |
| 27 |
5. USE="-* build bootstrap" emerge -e binutils gcc |
| 28 |
6. emerge -c |
| 29 |
7. USE="bootstrap" emerge -e gcc pam-login |
| 30 |
8. emerge -c |
| 31 |
That is _almost_ decent. It still leaves all C++ apps broken. |
| 32 |
If you want to go the CPU intensive route... 'emerge -e world' |
| 33 |
should fix it, otherwise you have to find an remerge all libs |
| 34 |
and bins that are broken. |
| 35 |
|
| 36 |
I recommend the scripts... They are painless. |
Archives