From: Peter Korsgaard <peter@korsgaard.com>
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>,
Woodrow Douglass <wdouglass@carnegierobotics.com>,
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 v2, 1/1] package/python-numpy: needs gcc >= 9
Date: Fri, 01 Dec 2023 21:21:36 +0100 [thread overview]
Message-ID: <87o7f94qsv.fsf@48ers.dk> (raw)
In-Reply-To: <20231104221206.12371-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 4 Nov 2023 23:12:06 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> 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
> Fixes:
> - http://autobuild.buildroot.org/results/9ec82be71c908873112064792ace283049355031
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2 (after review of Thomas Petazzoni):
> - Require gcc >= 9
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-01 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 22:12 [Buildroot] [PATCH v2,1/1] package/python-numpy: needs gcc >= 9 Fabrice Fontaine
2023-12-01 20:21 ` Peter Korsgaard [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=87o7f94qsv.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=asafka7@gmail.com \
--cc=buildroot@buildroot.org \
--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=wdouglass@carnegierobotics.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