From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: MIPS vs MIPS32 tunings -- summary and questions
Date: Mon, 16 Apr 2012 16:50:35 +0100 [thread overview]
Message-ID: <1334591435.616.5.camel@ted> (raw)
In-Reply-To: <4F8C2EA9.5090100@windriver.com>
On Mon, 2012-04-16 at 22:37 +0800, Robert Yang wrote:
>
> On 04/16/2012 09:55 PM, Andreas Oberritter wrote:
> > On 10.04.2012 21:28, Andreas Oberritter wrote:
> >> I'm fine with either way that restores mips/mipsel for mips32 targets
> >> *before the release*, because the online update feeds broke and all
> >> packages had to be built again from scratch.
> >
> > Richard, can you please state your opinion about this issue?
> >
> > The mips package feed (e.g. qemumips) is now broken since weeks. Can I
>
> I'm a little confused with this, I've just done a build with
> MACHINE = "qemumips", both build and runqemu worked well.
Builds will work fine however the package architecture for mips32
changes from "mipsel" to "mips32el" which broken things for people with
existing package feeds.
Cheers,
Richard
next prev parent reply other threads:[~2012-04-16 16:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 17:53 MIPS vs MIPS32 tunings -- summary and questions Mark Hatle
2012-04-10 19:28 ` Andreas Oberritter
2012-04-16 13:55 ` Andreas Oberritter
2012-04-16 14:37 ` Robert Yang
2012-04-16 15:23 ` Andreas Oberritter
2012-04-16 15:50 ` Richard Purdie [this message]
2012-04-16 14:42 ` Richard Purdie
2012-04-16 15:15 ` Andreas Oberritter
2012-04-16 15:30 ` Mark Hatle
2012-04-18 11:30 ` Andreas Oberritter
2012-04-18 11:40 ` Richard Purdie
2012-04-18 11:45 ` Andreas Oberritter
2012-04-18 11:53 ` Andreas Oberritter
2012-04-18 11:54 ` Martin Jansa
2012-04-18 12:00 ` Richard Purdie
2012-04-18 12:08 ` Andreas Oberritter
2012-04-18 12:45 ` Richard Purdie
2012-04-18 14:37 ` Andreas Oberritter
2012-04-18 15:21 ` Mark Hatle
2012-04-18 15:46 ` Martin Jansa
2012-04-18 17:01 ` Koen Kooi
2012-04-18 18:10 ` Andreas Oberritter
2012-04-18 18:31 ` Koen Kooi
2012-04-18 19:57 ` Martin Jansa
2012-04-18 12:15 ` Koen Kooi
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=1334591435.616.5.camel@ted \
--to=richard.purdie@linuxfoundation.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