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 15:53:25 -0500 [thread overview]
Message-ID: <20121023155325.73a904ac@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:
> How can I build test this, the same way as x32?
I am ... not entirely sure how you'd do it in the absence of an
n32 target. Our binary prebuilt toolchain uses n32 for one of the
Octeon parts.
I think any tuning that uses n32 should illustrate the failure modes in
the previous setup, which are:
1. First thing you build that has target binaries errors out with QA
checks because you're making 32-bit binaries for mips64.
2. Anything that wants ncurses ends up thinking that ncurses.h doesn't
exist because ncurses.h is a symlink to curses.h, and curses.h is
renamed to curses-64.h, but the #include magic in the wrapper looks for
curses-n32.h.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2012-10-23 21:07 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 [this message]
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=20121023155325.73a904ac@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox