From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/python-greenlet: add missing C++ dependency
Date: Sat, 28 Jan 2023 22:40:46 +0100 [thread overview]
Message-ID: <20230128224046.7b3165dd@windsurf> (raw)
In-Reply-To: <20230127050613.793962-1-james.hilliard1@gmail.com>
On Thu, 26 Jan 2023 22:06:13 -0700
James Hilliard <james.hilliard1@gmail.com> wrote:
> Fixes:
> - http://autobuild.buildroot.net/results/529/5291fe0fac1d5c7b6587e4a566991a764a2632fb
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> package/python-greenlet/Config.in | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/python-greenlet/Config.in b/package/python-greenlet/Config.in
> index 9f66ebe119..32ccdaae27 100644
> --- a/package/python-greenlet/Config.in
> +++ b/package/python-greenlet/Config.in
> @@ -12,6 +12,7 @@ config BR2_PACKAGE_PYTHON_GREENLET_ARCH_SUPPORTS
> config BR2_PACKAGE_PYTHON_GREENLET
> bool "python-greenlet"
> depends on BR2_PACKAGE_PYTHON_GREENLET_ARCH_SUPPORTS
> + depends on BR2_INSTALL_LIBSTDCPP
When a toolchain dependency like this is added a Config.in comment is
needed. I've added it and applied. Thanks!
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
prev parent reply other threads:[~2023-01-28 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 5:06 [Buildroot] [PATCH 1/1] package/python-greenlet: add missing C++ dependency James Hilliard
2023-01-27 5:14 ` Yegor Yefremov via buildroot
2023-01-28 21:40 ` 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=20230128224046.7b3165dd@windsurf \
--to=buildroot@buildroot.org \
--cc=asafka7@gmail.com \
--cc=james.hilliard1@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.