Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: bring mipsel support (little endian mode)
Date: Wed, 27 Jun 2012 08:09:36 +0100	[thread overview]
Message-ID: <1340780976.2886.1.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAF1ZMEcMxTQUhyHdmMWV_PA6TY=RTz9rq-EahKU0p=DFFPw+Ew@mail.gmail.com>

On Wed, 2012-06-27 at 14:25 +0800, Dennis.Yxun wrote:
>    for mipsel we also have to filter out -march=mips32, previously we
> only handle mips (the big endian?)

Why isn't mipsel getting the mips overrides?  I believe it's meant to.
For what it's worth, mipsel (generically; I haven't tried qemu
specifically) does seem to work fine for me without this patch.

p.





  parent reply	other threads:[~2012-06-27  7:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  6:25 bring mipsel support (little endian mode) Dennis.Yxun
2012-06-27  6:40 ` Khem Raj
2012-06-27  7:00   ` [yocto] " Dennis.Yxun
2012-06-27 12:49   ` Bruce Ashfield
2012-06-27  7:09 ` Phil Blundell [this message]
2012-06-27 15:41   ` Khem Raj
2012-06-27 15:17 ` Bruce Ashfield
2012-06-27 19:52   ` Dennis.Yxun

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=1340780976.2886.1.camel@x121e.pbcl.net \
    --to=philb@gnu.org \
    --cc=openembedded-core@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