| 1 |
Volker Armin Hemmann wrote: |
| 2 |
> On Mittwoch, 18. Juli 2007, Daniel da Veiga wrote: |
| 3 |
> |
| 4 |
>> On 7/18/07, Alex Schuster <wonko@×××××××××.org> wrote: |
| 5 |
>> |
| 6 |
>>> Another method, which I would use, would be to change your CFLAGS to what |
| 7 |
>>> you would like for the new processor, but use mtune= instead of march=. |
| 8 |
>>> This will also optimize for the cpu, but the code will run on any x86 |
| 9 |
>>> CPU. emerge world --emptytree to re-compile everything, then switch your |
| 10 |
>>> hardware. This will give you flexibility, at the cost of lesser |
| 11 |
>>> optimization. Depends on how you use your system, most applications will |
| 12 |
>>> not show a noticeable speed ddifference I guess. |
| 13 |
>>> You could also change to march= later, when the system ist up, and |
| 14 |
>>> re-compile everything again to get full optimization. |
| 15 |
>>> |
| 16 |
>> Oh, that's good to know, I guess that's the best option, since after |
| 17 |
>> the system is up and running I can do whatever optimizations it needs, |
| 18 |
>> as long as I'm able to boot and work with it in the new hardware. |
| 19 |
>> |
| 20 |
>> Tonight I'll start the (long and boring) process of recompiling the |
| 21 |
>> whole stuff with "-mtune" instead of "-march". |
| 22 |
>> |
| 23 |
>> Thanks to all that replied so far... Maybe more suggestions comming?! |
| 24 |
>> |
| 25 |
> |
| 26 |
> instead of two emerge --emptytree it would be faster to just nuke the |
| 27 |
> installation.... |
| 28 |
> |
| 29 |
|
| 30 |
I agree. Just back up /etc, make a copy of your world file and any |
| 31 |
other config files you may need and start from scratch. At least then |
| 32 |
you KNOW for sure where you started from and that something didn't get |
| 33 |
missed somewhere. |
| 34 |
|
| 35 |
Oh, don't forget /home either. |
| 36 |
|
| 37 |
Dale |
| 38 |
|
| 39 |
:-) :-) :-) |
Archives