1 |
On 7/18/07, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Wed, 18 Jul 2007 19:49:00 +0200, Alex Schuster wrote: |
3 |
> |
4 |
> > Another method, which I would use, would be to change your CFLAGS to |
5 |
> > what you would like for the new processor, but use mtune= instead of |
6 |
> > march=. This will also optimize for the cpu, but the code will run on |
7 |
> > any x86 CPU. emerge world --emptytree to re-compile everything, then |
8 |
> > switch your hardware. |
9 |
> |
10 |
> Recompiling everything is unnecessary, you only need to recompile those |
11 |
> packages that are necessary to get your system booting with the new |
12 |
> hardware. emerge -e system should do that, along with recompiling the |
13 |
> kernel. As long as you have a working toolchain, you can then recompile |
14 |
> anything important to you that fails to work on the new hardware before |
15 |
> resetting the CFLAGS and doing a background emerge -e world while getting |
16 |
> on with whatever you use the computer for. |
17 |
> |
18 |
> Don't forget to set PORTAGE_NICENESS in make.conf before you emerge -e |
19 |
> world. |
20 |
> |
21 |
|
22 |
I have read some docs that suggest what Mike said could happen to me, |
23 |
because some intructions set are not compatible, along with Neil |
24 |
suggestion and Alex advice, I decided to recompile "system" with the |
25 |
new "-mtune" instead of "-march" tonight. I'll just see if it works by |
26 |
simply booting the new hardware and starting tunning. |
27 |
|
28 |
If something goes wrong, I can always go with Neil and Dale suggestion |
29 |
and start fresh, get /etc and /home, along with the world file, and |
30 |
let portage do the hard work. |
31 |
|
32 |
-- |
33 |
Daniel da Veiga |
34 |
Computer Operator - RS - Brazil |
35 |
-----BEGIN GEEK CODE BLOCK----- |
36 |
Version: 3.1 |
37 |
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- |
38 |
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ |
39 |
------END GEEK CODE BLOCK------ |
40 |
-- |
41 |
gentoo-user@g.o mailing list |