From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/refpolicy: needs python3
Date: Thu, 16 Jul 2020 23:06:25 +0200 [thread overview]
Message-ID: <20200716230625.54fd0280@windsurf.home> (raw)
In-Reply-To: <20200716205939.1965929-1-fontaine.fabrice@gmail.com>
On Thu, 16 Jul 2020 22:59:39 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Commit 09b94b1e8f94d1f49f7a2349b4c8cbfecefa73da forgot to propagate
> python3 dependency from host-setools to refpolicy
>
> Fixes:
> - http://autobuild.buildroot.org/results/fdeaa54355aa0741eccc7864b034a7b07ef0c4bc
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/refpolicy/Config.in | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/package/refpolicy/Config.in b/package/refpolicy/Config.in
> index b50b2f09ff..e374ab1901 100644
> --- a/package/refpolicy/Config.in
> +++ b/package/refpolicy/Config.in
> @@ -1,5 +1,6 @@
> config BR2_PACKAGE_REFPOLICY
> bool "refpolicy"
> + depends on BR2_PACKAGE_PYTHON3 # host-setools
It is not possible for host-setools (a host package) to have a
dependency on python3, which is a target package.
However, what is possible is that when BR2_PACKAGE_PYTHON=y, the
default host Python version is Python 2.x, and therefore host-setools
gets installed for Python 2.x, but the refpolicy build uses
host-python3, so it does not find host-setools.
I think the correct fix is instead to set
HOST_SETOOLS_NEEDS_HOST_PYTHON = python3 since anyway it only works
with Python 3.x.
Antoine: any thoughts on this ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-07-16 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 20:59 [Buildroot] [PATCH 1/1] package/refpolicy: needs python3 Fabrice Fontaine
2020-07-16 21:06 ` Thomas Petazzoni [this message]
2020-07-17 7:20 ` Antoine Tenart
2020-07-27 13:10 ` Thomas Petazzoni
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=20200716230625.54fd0280@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 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.