Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Make n32 survive insane.bbclass and multilib_header
Date: Tue, 23 Oct 2012 15:32:13 -0500	[thread overview]
Message-ID: <cover.1351024134.git.peter.seebach@windriver.com> (raw)

The multilib_header fixup has code in the generated header to handle
n32, but doesn't detect n32 headers. Meanwhile, insane.bclass rejects
n32 binaries for being 32-bit binaries in a mips64 build. Solution: Use
an ABI suffix, and check for it in appropriate places.

Signed-off-by: Peter Seebach <peter.seebach@windriver.com>

The following changes since commit 754ddbf1c57e6b9d0650498538840effebe4f7a2:
  Ross Burton (1):
        libical: remove

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib seebs/mips64
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/mips64

Peter Seebach (1):
  insane.bbclass and friends: Fix sanity checks and multlib headers for
    n32

 meta/classes/insane.bbclass                  |    4 +++
 meta/classes/multilib_header.bbclass         |   32 +++++++++++++++++--------
 meta/conf/machine/include/mips/arch-mips.inc |    1 +
 3 files changed, 27 insertions(+), 10 deletions(-)




             reply	other threads:[~2012-10-23 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-23 20:32 Peter Seebach [this message]
2012-10-23 20:32 ` [PATCH 1/1] insane.bbclass and friends: Fix sanity checks and multlib headers for n32 Peter Seebach
2012-10-23 20:49 ` [PATCH 0/1] Make n32 survive insane.bbclass and multilib_header Saul Wold
2012-10-23 20:53   ` Peter Seebach
2012-10-23 21:47   ` 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.1351024134.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