[OE-core] [PATCH 5/3] conf/machine/include: Start to fill out architecture specific tune include files and tune features
Tom Rini
tom_rini at mentor.com
Mon Jul 25 20:43:19 UTC 2011
On 07/25/2011 01:39 PM, Phil Blundell wrote:
> On Mon, 2011-07-25 at 12:34 -0700, Tom Rini wrote:
>> On 07/25/2011 11:55 AM, Mark Hatle wrote:
>>> I actually prefer "x86-64" I think that is a reasonable compromise between the
>>> x86_64 naming and the need to not use "_".
>>
>> That causes other problems, no? Top of my head would be that deb/ipk
>> doesn't allow a dash in that field. Could be mistaken tho...
>
> The package management backend could always rewrite it to something else
> (under control of the DISTRO if need be, so AMD and Intel folks can each
> call it their own thing if they want to).
>
> Personally though, I would be tempted just to call it "x64", which is
> then nicely symmetric with x32 and doesn't seem likely to collide with
> anything else.
Yeah, but x32 means something else (not i586, etc) :) My main
suggestion is to follow existing conventions, so amd64 since we can't
match x86_64 like the RPM world. FWIW, x64 appears to be the MS ABI for
this case, so.. not a bad idea?
--
Tom Rini
Mentor Graphics Corporation
More information about the Openembedded-core
mailing list