All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Romain Naour <romain.naour@gmail.com>,
	Samuel Martin <s.martin49@gmail.com>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-numpy: needs C++
Date: Sat, 25 Feb 2023 22:02:42 +0100	[thread overview]
Message-ID: <20230225220242.2761cbe6@windsurf> (raw)
In-Reply-To: <20230225144904.3033289-1-fontaine.fabrice@gmail.com>

On Sat, 25 Feb 2023 15:49:04 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> C++ is mandatory since at least version 1.23.0 and
> https://github.com/numpy/numpy/commit/c91a7d0c5691c9d78bd75284777fda73f225155d
> resulting in the following build failure since bump to version 1.23.4 in
> commit 32d8e23b977a5bba1f23e3821709c6aa9ff3bc55:
> 
> RuntimeError: Broken toolchain: cannot link a simple C++ program. note: A compiler with support for C++11 language features is required.
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/2d048d9b669ad60f37eeb2162b0a4f9fb425be1e
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/piglit/Config.in       | 6 ++++--
>  package/python-numpy/Config.in | 6 ++++--
>  package/python-zlmdb/Config.in | 6 ++++--
>  3 files changed, 12 insertions(+), 6 deletions(-)

Applied to master, thanks.

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

  reply	other threads:[~2023-02-25 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 14:49 [Buildroot] [PATCH 1/1] package/python-numpy: needs C++ Fabrice Fontaine
2023-02-25 21:02 ` Thomas Petazzoni via buildroot [this message]
2023-03-14  7:27 ` Peter Korsgaard

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=20230225220242.2761cbe6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=fontaine.fabrice@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.