From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: x86_64
Date: Tue, 10 May 2011 20:43:22 +0200 [thread overview]
Message-ID: <20110510184322.GB7657@mx.loc> (raw)
In-Reply-To: <1305049907.3355.99.camel@lenovo.internal.reciva.com>
On Tue, May 10, 2011 at 06:51:47PM +0100, Phil Blundell wrote:
>On Tue, 2011-05-10 at 18:15 +0200, Bernhard Reutner-Fischer wrote:
>> On Tue, May 10, 2011 at 11:06:44AM +0100, Phil Blundell wrote:
>> >"x86_64" seems to be what's currently used as the architecture name. If
>>
>> That doesn't work as arch-dependent e.g. append, does it.
>>
>> FOO_append_x86_64 = '-mcpu=barcelona'
>
>It seems to work just fine for me. What goes wrong for you?
It was OVERRIDES as Enrico mentioned.
Given that both khem in (IIRC) 2009 and me a year later stumbled across
the name and abandoned the thing in consequence, settling on an example
name would be nice -- nowadays i would just use amd64 but that won't
happen anytime soon, unfortunately.
Both patches should be in the old patchwork, for reference.
cheers,
next prev parent reply other threads:[~2011-05-10 18:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 8:13 x86_64 Jaap de Jong
2011-05-10 10:00 ` x86_64 Bernhard Reutner-Fischer
2011-05-10 10:04 ` x86_64 Eric Bénard
2011-05-10 10:06 ` x86_64 Phil Blundell
2011-05-10 11:02 ` x86_64 Jaap de Jong
2011-05-10 11:08 ` x86_64 Phil Blundell
2011-05-10 11:15 ` x86_64 Jaap de Jong
2011-05-10 12:57 ` x86_64 Jaap de Jong
2011-05-10 14:38 ` x86_64 Phil Blundell
2011-05-10 15:04 ` x86_64 Jaap de Jong
2011-05-10 15:35 ` x86_64 Enrico Scholz
2011-05-10 15:47 ` x86_64 Michael Smith
2011-05-10 16:43 ` x86_64 Enrico Scholz
2011-05-10 16:15 ` x86_64 Bernhard Reutner-Fischer
2011-05-10 16:18 ` x86_64 Michael Smith
2011-05-10 17:51 ` x86_64 Phil Blundell
2011-05-10 18:43 ` Bernhard Reutner-Fischer [this message]
2011-05-10 16:38 ` x86_64 Enrico Scholz
2011-05-10 20:30 ` x86_64 Phil Blundell
2011-05-11 10:07 ` x86_64 Enrico Scholz
2011-05-15 22:11 ` x86_64 Khem Raj
2011-05-16 11:08 ` x86_64 Phil Blundell
-- strict thread matches above, loose matches on Subject: below --
2007-04-03 13:28 x86_64 Lucas Diaz
2005-07-28 15:00 X86_64 Nakajima, Jun
2005-07-28 14:40 X86_64 David_Wolinsky
2005-03-01 18:15 x86_64 Ian Pratt
2005-03-01 18:52 ` x86_64 Matt Ayres
2005-03-01 16:01 x86_64 Puthiyaparambil, Aravindh
2005-03-01 17:42 ` x86_64 Keir Fraser
2005-02-27 13:21 x86_64 Franck
2005-02-27 13:47 ` x86_64 Keir Fraser
2005-02-28 3:51 ` x86_64 Ronald G. Minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110510184322.GB7657@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.