| 1 |
On 6/14/06, Daniel da Veiga <danieldaveiga@×××××.com> wrote: |
| 2 |
> On 6/14/06, Jesse Hannah <jesse.hannah@×××××.com> wrote: |
| 3 |
> > 2. If I want to upgrade and rebuild my entire system (using a new gcc), is: |
| 4 |
> > emerge -u gcc |
| 5 |
> > emerge -e world |
| 6 |
> > the right thing to do? Am I missing anything there? |
| 7 |
> |
| 8 |
> http://www.gentoo.org/doc/en/gcc-upgrading.xml |
| 9 |
> Has everything you need to know... |
| 10 |
|
| 11 |
Yes, definitely follow the guide. |
| 12 |
|
| 13 |
During the emege -e world, if you use MAKEOPTS=-jN, where N>1, you may |
| 14 |
notice some things fail to build (at least I did). Doing a |
| 15 |
"MAKEOPTS=-j1 emerge -e --resume world" is the way around most |
| 16 |
problems. |
| 17 |
|
| 18 |
Also, if you use KDE, you may want to checkout the kdehiddenvisibility |
| 19 |
flag before commencing the emerge -e world. Setting it should improve |
| 20 |
KDE startup times. I can't say I noticed a dramatic speedup, but my |
| 21 |
laptop is definitely at the high-end of the performance range... |
| 22 |
|
| 23 |
-Richard |
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives