Lunar optimize

[Guillaume]

> On 09/28/2010 02:59 PM, Guillaume wrote:
>> Hello,
>>
>> It seems lunar changed the way we can define the CPU with GCC 4.5 in "lunar optimize".
>>
>> I don't want to use native on my core2 because I sometime create modules for my slow atom
>> computer.
>> With GCC 4.4 I can select any architecture I want :)
>> With GCC 4.5 I only "native" is available  :(  (I don't know architecture "None")
>>
>> Is there any plan to add more architecture to GCC 4.5 settings ?
>> If not I'll manually modify /etc/lunar/local/optimizations.GCC_4_5, could you please confirm
>> that updates of lunar module will not overwrite this file.
>
> Native is correct as base optimization for your atom processor. That's
> what you should use.
>
> Auke
>

I agree that native is the correct optimization for any computer that compile modules for itself.
But my atom also use applications compiled by another PC ... so I can't set native the other PC.
This may looks strange to you but it save me a lot of time :)

I just hope that CPU=native will not be hard-coded in lunar code but will remain in
optimizations.GCC_4_5 file.

Drew is true ... I should have a look at distcc, I just don't know how complicated it is (this is
why up to know I share some compiled modules between computers).

Guillaume