| 1 |
On Wed, 18 Jul 2007 19:49:00 +0200, Alex Schuster wrote: |
| 2 |
|
| 3 |
> Another method, which I would use, would be to change your CFLAGS to |
| 4 |
> what you would like for the new processor, but use mtune= instead of |
| 5 |
> march=. This will also optimize for the cpu, but the code will run on |
| 6 |
> any x86 CPU. emerge world --emptytree to re-compile everything, then |
| 7 |
> switch your hardware. |
| 8 |
|
| 9 |
Recompiling everything is unnecessary, you only need to recompile those |
| 10 |
packages that are necessary to get your system booting with the new |
| 11 |
hardware. emerge -e system should do that, along with recompiling the |
| 12 |
kernel. As long as you have a working toolchain, you can then recompile |
| 13 |
anything important to you that fails to work on the new hardware before |
| 14 |
resetting the CFLAGS and doing a background emerge -e world while getting |
| 15 |
on with whatever you use the computer for. |
| 16 |
|
| 17 |
Don't forget to set PORTAGE_NICENESS in make.conf before you emerge -e |
| 18 |
world. |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Neil Bothwick |
| 23 |
|
| 24 |
Nymphomania-- an illness you hear about but never encounter. |
Archives