Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Didin <Evgeniy.Didin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2]python-numpy: disable for ARCompact
Date: Thu,  9 Nov 2017 12:53:48 +0300	[thread overview]
Message-ID: <20171109095348.31755-2-didin@synopsys.com> (raw)
In-Reply-To: <20171109095348.31755-1-didin@synopsys.com>

This package fails when building for ARCompact due to toolchain issue.

Marking this with special comment "#ARC toolchain issues for ARCompact"
as the package is to be enabled as soon as the issue with the ARC toolchain is resolved.
Fixes:
        http://autobuild.buildroot.net/results/4c4/4c4eaa90335756448007ae3c5ae3839fb17d4442//

The same compiler error appears building "trousers" package for ARCompact. This package
is already disabled for ARC.

Signed-off-by: Evgeniy Didin <didin@synopsys.com>
Cc: Alexey Brodkin <abrodkin@synopsys.com>
Cc: arc-buildroot at synopsys.com
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

---
Changes since v1:
-Removed duplicate entry in BR2_PACKAGE_PYTHON_NUMPY
-Now disables python-numpy accordingly to new format

 package/python-numpy/Config.in | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/package/python-numpy/Config.in b/package/python-numpy/Config.in
index 5abe04bde9..97d706178f 100644
--- a/package/python-numpy/Config.in
+++ b/package/python-numpy/Config.in
@@ -1,7 +1,8 @@
 config BR2_PACKAGE_PYTHON_NUMPY_ARCH_SUPPORTS
 	bool
 	# Numpy has some CPU specific code
-	default y if BR2_arc 
+        # ARC toolchain issues for ARCompact
+	default y if BR2_arc && !(BR2_arc770d || BR2_arc750d)
 	default y if BR2_aarch64
 	default y if BR2_arm 
 	default y if BR2_armeb
-- 
2.11.0

      reply	other threads:[~2017-11-09  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09  9:53 [Buildroot] [PATCH] python-numpy: reformat Config.in variable Evgeniy Didin
2017-11-09  9:53 ` Evgeniy Didin [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=20171109095348.31755-2-didin@synopsys.com \
    --to=evgeniy.didin@synopsys.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