From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/python-numpy: fix fenv build failure on ARC with glibc
Date: Mon, 14 Jan 2019 21:40:58 +0100 [thread overview]
Message-ID: <20190114214058.423cb7f4@windsurf> (raw)
In-Reply-To: <20190114154316.47795-1-Evgeniy.Didin@synopsys.com>
Hello,
On Mon, 14 Jan 2019 18:43:16 +0300, Evgeniy Didin wrote:
> Building python-numpy on ARC with glibc fails due to missing FE_*
> definitions in <fenv.h>. These exceptions are not supported by
> ARC architecture. Let's add patch, which disables compilation
> of a part of the code in which FE_* errors occur for ARC.
>
> ARCompact toolchain issues are already fixed in the latest toolchain.
> Also since commit "311af5e8c2db887800639bc803c8201b6b70e9ce"
> ("toolchain/toolchain-buildroot: enable glibc for all little-endian
> ARCs with atomic ops") glibc is available for ARCompact.
> That is why in Config.in we are leaving only "BR_arc" and
> removing comments, which are not actual.
>
> Signed-off-by: Evgeniy Didin <didin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: arc-buildroot at synopsys.com
> ---
> Changes since v1:
> -Modify patch according to uClibc patch
> -Remove irrelevant comments in Config.in
> -Update commit message and title
> .../0003-no-FPU-exceptions-bits-on-ARC-glibc.patch | 42 ++++++++++++++++++++++
> package/python-numpy/Config.in | 4 +--
> 2 files changed, 43 insertions(+), 3 deletions(-)
> create mode 100644 package/python-numpy/0003-no-FPU-exceptions-bits-on-ARC-glibc.patch
Applied to master, thanks. Please submit the patch upstream if not
already done. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-14 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 15:43 [Buildroot] [PATCH v2] package/python-numpy: fix fenv build failure on ARC with glibc Evgeniy Didin
2019-01-14 20:40 ` Thomas Petazzoni [this message]
2019-01-24 16:22 ` Peter Korsgaard
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=20190114214058.423cb7f4@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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