Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: x86_64
Date: Wed, 11 May 2011 12:07:40 +0200	[thread overview]
Message-ID: <ly62phpn2r.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <1305059419.3355.108.camel@lenovo.internal.reciva.com> (Phil Blundell's message of "Tue, 10 May 2011 21:30:19 +0100")

Phil Blundell <philb@gnu.org> writes:

> Changing the architecture to x86-64 would be a possibility, 

no; will cause too much pain because all the ./config.guess scripts
expect 'x86_64'.

I kept TARGET_ARCH='x86_64' but added an additional OVERRIDES where '_'
is replaced by '-'.


Enrico



  reply	other threads:[~2011-05-11 10:10 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   ` 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         ` 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         ` Enrico Scholz [this message]
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=ly62phpn2r.fsf@ensc-virt.intern.sigma-chemnitz.de \
    --to=enrico.scholz@sigma-chemnitz.de \
    --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