From: Randy MacLeod <randy.macleod@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] valgrind: drop mips n32 support
Date: Thu, 8 Nov 2018 10:09:35 -0500 [thread overview]
Message-ID: <93b145d4-20f8-8f60-38dc-e94f0d3db32f@windriver.com> (raw)
In-Reply-To: <CAJTo0LaNF-q9Lj6-VZgnGbX154hO_XOx7KaKzxcAzys1WBBnPg@mail.gmail.com>
On 11/8/18 9:14 AM, Burton, Ross wrote:
> On Wed, 7 Nov 2018 at 18:00, Randy MacLeod <Randy.MacLeod@windriver.com> wrote:
>> valgrind for qemumips64 multilib builds fails to configure
>> for libn32 with the error:
>> configure:6190: checking for 32 bit build support
>> ...
>> fatal error: bits/long-double-32.h: No such file or directory
>> It seems that the toolchain is producing:
>> tmp-glibc/sysroots-components/mips64-n32/libn32-glibc/usr/include/bits/long-double-n32.h
>>
>> Until the toolchain problem is resolved, skip valgrind for libn32.
>
> Is there a bug filed for this?
Of course there's a bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12989
(now).
>
> Ross
>
--
# Randy MacLeod
# Wind River Linux
prev parent reply other threads:[~2018-11-08 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:59 [PATCH] valgrind: drop mips n32 support Randy MacLeod
2018-11-08 14:14 ` Burton, Ross
2018-11-08 15:09 ` Randy MacLeod [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=93b145d4-20f8-8f60-38dc-e94f0d3db32f@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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.