From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] MIPS n32 shouldn't have SITEINFO_BITS = "64"
Date: Thu, 21 Feb 2013 11:40:21 -0600 [thread overview]
Message-ID: <cover.1361468282.git.peter.seebach@windriver.com> (raw)
MIPS n32 is a mips64 which is 32 bit. This historical quirk is recognized
by insane.bbclass (except for a typo I made in a previous patch, also
fixed here), but siteinfo doesn't know, so various programs fail to build
correctly for it because SITEINFO_BITS is telling them they are 64-bit
builds. (We ran into this with nss, which isn't in oe-core that I know
of.)
So, add "bit-32" to mips-linux-gnun32's feature list (the SITEINFO_BITS
test checks for 32 first, 64 second, so I don't have to remove bit-64),
and remove the nonexistent mips-linux-gnun32 cases. Likewise for
mipsel/mips64el.
The following changes since commit a5362de60c0051f16b88a40bd9cb41915bee0b0f:
Ross Burton (1):
rootfs_ipkg: fix BAD_RECOMMENDATIONS handling
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/gnun32
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/gnun32
Peter Seebach (1):
More n32 fixups
meta/classes/insane.bbclass | 2 +-
meta/classes/siteinfo.bbclass | 6 ++----
2 files changed, 3 insertions(+), 5 deletions(-)
next reply other threads:[~2013-02-21 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 17:40 Peter Seebach [this message]
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
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=cover.1361468282.git.peter.seebach@windriver.com \
--to=peter.seebach@windriver.com \
--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