From: Peter Seebach <peter.seebach@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] Make n32 survive insane.bbclass and multilib_header
Date: Tue, 23 Oct 2012 16:47:53 -0500 [thread overview]
Message-ID: <20121023164753.0dcdcd17@e6410-2> (raw)
In-Reply-To: <508702EA.6090800@linux.intel.com>
On Tue, 23 Oct 2012 13:49:46 -0700
Saul Wold <sgw@linux.intel.com> wrote:
> On 10/23/2012 01:32 PM, Peter Seebach wrote:
> > 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.
> >
>
> How can I build test this, the same way as x32?
And to save you trouble, I don't know how it passed my first test build,
because it obviously fails now on glib. Solution seems to be:
+++ b/meta/classes/siteinfo.bbclass
@@ -50,6 +50,7 @@ def siteinfo_data(d):
"linux": "common-linux common-glibc",
"linux-gnu": "common-linux common-glibc",
"linux-gnux32": "common-linux common-glibc",
+ "linux-gnun32": "common-linux common-glibc",
so I'll retest with that and resubmit.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2012-10-23 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 20:32 [PATCH 0/1] Make n32 survive insane.bbclass and multilib_header Peter Seebach
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 [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=20121023164753.0dcdcd17@e6410-2 \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.