Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-numpy: re-enable for uClibc
Date: Sun, 4 Oct 2015 17:51:15 +0100	[thread overview]
Message-ID: <20151004175115.7be4e036@free-electrons.com> (raw)
In-Reply-To: <1443972881-24357-1-git-send-email-arnout@mind.be>

Dear Arnout Vandecappelle (Essensium/Mind),

On Sun, 4 Oct 2015 16:34:41 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> In commit b0f025386f6861fdc21e38e3a33b65669276f2c2 a patch was added
> to make sure that python-numpy does work in uClibc. This patch was
> needed for the x86 architecture, because uClibc in fact does support
> fenv for x86. However, we don't turn on this support in our uClibc
> config. Because the Config.in depends still allowed uClibc for x86,
> this lead to a built failure, which lead to the fix in commit b0f02538.
> But since this fix also fixes it for all other (supported)
> architectures, we can just remove the !uClibc dependency completely.
> 
> This is also propagated to the reverse dependency in opencv3.
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
> ---
>  package/opencv3/Config.in      | 1 -
>  package/python-numpy/Config.in | 3 ---
>  2 files changed, 4 deletions(-)

Applied, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2015-10-04 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 15:34 [Buildroot] [PATCH] python-numpy: re-enable for uClibc Arnout Vandecappelle
2015-10-04 16:51 ` Thomas Petazzoni [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=20151004175115.7be4e036@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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