| 1 |
Marcin Cieslak <saper <at> saper.info> writes: |
| 2 |
|
| 3 |
|
| 4 |
> If compiler does not work in the current stage3 maybe this is a bug? |
| 5 |
> (Completely unrelated to my upgrade problems). |
| 6 |
|
| 7 |
Yes there is a gambit of compiler bugs. It can waste time. I just upgraded to |
| 8 |
the next one up and tried to compile from then. You have to use concurrent |
| 9 |
compilers with the date of portage, for best results. |
| 10 |
|
| 11 |
> Thanks. I'll try going upgrading portage version-by-version. |
| 12 |
|
| 13 |
One other thing I did, after a few of these. I dropped the profile |
| 14 |
down to the basic (default) |
| 15 |
|
| 16 |
for me that's |
| 17 |
[1] default/linux/amd64 |
| 18 |
|
| 19 |
Once a system is updated you can move your world file back, or portions |
| 20 |
of it and enhance the profile as you like. |
| 21 |
|
| 22 |
|
| 23 |
There are other things like the location of portage that can cause minor |
| 24 |
issues. |
| 25 |
|
| 26 |
Also look at the old news items if you get stumped on something. They |
| 27 |
are dated so you can coordinate with the date of the portage you are |
| 28 |
on as you update, for any other gotchas..... |
| 29 |
|
| 30 |
|
| 31 |
Sometimes a fresh install is a good idea. Make sure all your system |
| 32 |
fans are in place and running to keep the system cool as you compile. |
| 33 |
|
| 34 |
hth, |
| 35 |
James |
Archives