Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Jugurtha BELKALEM <jugurtha.belkalem@smile.fr>,
	Samuel Martin <s.martin49@gmail.com>,
	Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
	Guillaume William Brs <guillaume.bressaix@gmail.com>,
	Asaf Kahlon <asafka7@gmail.com>, Julien Olivain <ju.o@free.fr>,
	Jagan Teki <jagan@amarulasolutions.com>,
	buildroot@buildroot.org,
	James Hilliard <james.hilliard1@gmail.com>,
	Romain Naour <romain.naour@gmail.com>,
	Mauro Condarelli <mc5686@mclink.it>
Subject: Re: [Buildroot] [PATCH 1/1] package/python-numpy: needs gcc >= 8
Date: Sat, 4 Nov 2023 22:59:50 +0100	[thread overview]
Message-ID: <20231104225950.1b294a18@windsurf> (raw)
In-Reply-To: <20230930221051.231730-1-fontaine.fabrice@gmail.com>

On Sun,  1 Oct 2023 00:10:51 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> python-numpy needs gcc >= 8.4 since bump to version 1.25.0 in commit
> ca63464e3777ca2596b4d396accb6a384ccf8514 and
> https://github.com/numpy/numpy/commit/4002a7d421ff10780c28a3643683af7a9754f87f:
> 
> ../output-1/build/host-python-numpy-1.25.0/meson.build:30:4: ERROR: Problem encountered: NumPy requires GCC >= 8.4

Then we need to require gcc >= 9, because BR2_TOOLCHAIN_GCC_AT_LEAST_8
or BR2_HOST_GCC_AT_LEAST_8, only guarantee gcc 8.x, not 8.4, so a user
with gcc 8.3 would still be in trouble.

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-11-04 22:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-30 22:10 [Buildroot] [PATCH 1/1] package/python-numpy: needs gcc >= 8 Fabrice Fontaine
2023-11-04 21:59 ` Thomas Petazzoni via buildroot [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=20231104225950.1b294a18@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=fontaine.fabrice@gmail.com \
    --cc=guillaume.bressaix@gmail.com \
    --cc=gwenhael.goavec-merou@trabucayre.com \
    --cc=jagan@amarulasolutions.com \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=jugurtha.belkalem@smile.fr \
    --cc=mc5686@mclink.it \
    --cc=romain.naour@gmail.com \
    --cc=s.martin49@gmail.com \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox