From: Peter Seebach <peter.seebach@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc: 0041-handle-target-sysroot-multilib.patch maybe doesn't work for n32?
Date: Tue, 13 Oct 2015 16:26:02 -0500 [thread overview]
Message-ID: <20151013162602.2af8876f@seebs-worktop> (raw)
In-Reply-To: <CAMKF1sou00wtaW=5R4srchBMEswv4NZEJXfqT-rpoyV61p94xg@mail.gmail.com>
On Tue, 13 Oct 2015 14:16:53 -0700
Khem Raj <raj.khem@gmail.com> wrote:
> also look at 0013-64-bit-multilib-hack.patch
> this should not even look at bitness directories. I wonder why thats happening.
I don't know. I know that we didn't have this problem in the 4.9 era, but I
think that our toolchain had 64-bit-multilib.patch back then, but didn't have
the newer handle-target-sysroot-multilib. I haven't tried building without
them yet to see how different it is (or isn't). It may also be a 5.2 change.
Wheeeeeee.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
prev parent reply other threads:[~2015-10-13 21:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 19:00 gcc: 0041-handle-target-sysroot-multilib.patch maybe doesn't work for n32? Peter Seebach
2015-10-13 21:16 ` Khem Raj
2015-10-13 21:26 ` 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=20151013162602.2af8876f@seebs-worktop \
--to=peter.seebach@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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