From: Peter Seebach <peter.seebach@windriver.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] More n32 fixups
Date: Thu, 21 Feb 2013 17:31:50 -0600 [thread overview]
Message-ID: <20130221173150.5a8764e4@e6410-2> (raw)
In-Reply-To: <13cff11cfb1.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com>
On Fri, 22 Feb 2013 00:23:48 +0100
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> wrote:
> > Also, the insane.bbclass change spelled "mips64el" as "mipsel64",
> > which no one noticed because no one's using little-endian n32,
> > apparently.
>
> Would be great if you could have a look at the FIXME in
> meta/recipes-core/uclibc/uclibc-config.inc for the correct setting of
> the respective mips ABI.
Hmm. I can look, but I don't think I've touched uclibc in a fairly
long time. Untested, but possibly pretty close:
--- a/meta/recipes-core/uclibc/uclibc-config.inc
+++ b/meta/recipes-core/uclibc/uclibc-config.inc
@@ -73,9 +73,11 @@ def map_uclibc_abi(o, d):
return 'ARM_EABI'
else:
return 'ARM_OABI'
- # FIXME: This is inaccurate! Handle o32, n32, n64
elif re.match('^mips.*64$', arch):
- return 'MIPS_N64_ABI'
+ if o.endswith('gnun32'):
+ return 'MIPS_N32_ABI'
+ else:
+ return 'MIPS_N64_ABI'
elif re.match('^mips.*', arch):
return 'MIPS_O32_ABI'
return ""
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2013-02-21 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 17:40 [PATCH 0/1] MIPS n32 shouldn't have SITEINFO_BITS = "64" Peter Seebach
2013-02-21 17:40 ` [PATCH 1/1] More n32 fixups Peter Seebach
[not found] ` <13cff0cc5c1.2760.0f39ed3bcad52ef2c88c90062b7714dc@gmail.com>
2013-02-21 23:23 ` Bernhard Reutner-Fischer
2013-02-21 23:31 ` Peter Seebach [this message]
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=20130221173150.5a8764e4@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rep.dot.nop@gmail.com \
/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