From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: x86_64
Date: Tue, 10 May 2011 11:06:44 +0100 [thread overview]
Message-ID: <1305022004.8000.149.camel@phil-desktop> (raw)
In-Reply-To: <20110510100020.GA10493@mx.loc>
On Tue, 2011-05-10 at 12:00 +0200, Bernhard Reutner-Fischer wrote:
> On Tue, May 10, 2011 at 10:13:22AM +0200, Jaap de Jong wrote:
> >Hi All,
> >
> >is there any support for 64 bit intel/amd machines?
> >And if so, how to build for them?
>
> Can we settle on a name please for i want to add a qemu machine for
> testing x86_64?
>
> x8664
> amd64
> ...
>
> Opinions?
"x86_64" seems to be what's currently used as the architecture name. If
you want a value for ${MACHINE} then I guess something like
"x86_64-generic" would do. I don't think there's any prohibition
against underscores in machine names.
p.
next prev parent reply other threads:[~2011-05-10 10:09 UTC|newest]
Thread overview: 22+ 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 ` Phil Blundell [this message]
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 ` x86_64 Bernhard Reutner-Fischer
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
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=1305022004.8000.149.camel@phil-desktop \
--to=philb@gnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox