Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v8 1/5] package/python-numpy: Bump to version 1.18.2
Date: Fri, 1 May 2020 14:37:15 +0200	[thread overview]
Message-ID: <20200501143715.316f5bb5@windsurf.home> (raw)
In-Reply-To: <20200407111515.21131-2-jagan@amarulasolutions.com>

Hello,

I've applied, after doing some fixes. See below.

On Tue,  7 Apr 2020 16:45:11 +0530
Jagan Teki <jagan@amarulasolutions.com> wrote:

> Bump the python-numpy version to 1.18.2, this version
> of python-numpy will support python3 only, not python2.

Why "will" ? It does only support Python 3, today.

Also, you forgot to explain why host-python-cython was needed.

I've reworded the commit log to fix those details.

> diff --git a/package/gnuradio/gnuradio.mk b/package/gnuradio/gnuradio.mk
> index 41d4619f72..ab5b79e3e5 100644
> --- a/package/gnuradio/gnuradio.mk
> +++ b/package/gnuradio/gnuradio.mk
> @@ -13,7 +13,7 @@ GNURADIO_SUPPORTS_IN_SOURCE_BUILD = NO
>  
>  # host-python-mako and host-python-six are needed for volk to compile
>  GNURADIO_DEPENDENCIES = \
> -	$(if $(BR2_PACKAGE_PYTHON3),host-python3,host-python) \
> +	host-python3 \

This wasn't good. Indeed, gnuradio, when its python support is not
enabled, can still build with host-python.

It would in fact not even use host-python3 here if BR2_PACKAGE_PYTHON=y.

So I simply dropped this line.


> diff --git a/package/python-numpy/Config.in b/package/python-numpy/Config.in
> index 5b9ee5803b..507d52c4d8 100644
> --- a/package/python-numpy/Config.in
> +++ b/package/python-numpy/Config.in
> @@ -15,6 +15,7 @@ config BR2_PACKAGE_PYTHON_NUMPY_ARCH_SUPPORTS
>  
>  config BR2_PACKAGE_PYTHON_NUMPY
>  	bool "python-numpy"
> +	depends on BR2_PACKAGE_PYTHON3

You forgot to propagate this dependency to the Config.in comment in the
same file, so I fixed that.

> +PYTHON_NUMPY_DEPENDENCIES += host-python-cython
> +HOST_PYTHON_NUMPY_DEPENDENCIES += host-python-cython

= signs were enough here.

Applied with those various issues fixed. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-05-01 12:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 11:15 [Buildroot] [PATCH v8 0/5] package/python-scipy: new package Jagan Teki
2020-04-07 11:15 ` [Buildroot] [PATCH v8 1/5] package/python-numpy: Bump to version 1.18.2 Jagan Teki
2020-05-01 12:37   ` Thomas Petazzoni [this message]
2020-04-07 11:15 ` [Buildroot] [PATCH v8 2/5] package/python-numpy: fixup npymath.ini for numpy extensions Jagan Teki
2022-01-07 22:10   ` Arnout Vandecappelle
2020-04-07 11:15 ` [Buildroot] [PATCH v8 3/5] package/python-pybind11: new host package Jagan Teki
2020-04-07 11:15 ` [Buildroot] [PATCH v8 4/5] support/testing: add python-pybind11 test Jagan Teki
2022-01-07 21:38   ` Arnout Vandecappelle
2020-04-07 11:15 ` [Buildroot] [PATCH v8 5/5] package/python-scipy: new package Jagan Teki
2022-01-07 23:12   ` Arnout Vandecappelle
2020-04-07 11:49 ` [Buildroot] [PATCH v8 0/5] " Thomas Petazzoni
2020-04-07 13:43   ` Jagan Teki
2020-04-07 15:01     ` Yann E. MORIN
2020-04-07 16:18       ` Jagan Teki
2020-07-03  8:09         ` Jagan Teki

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=20200501143715.316f5bb5@windsurf.home \
    --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