Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: "Etienne Carriere" <etienne.carriere@linaro.org>,
	"Clément Léger" <clement.leger@bootlin.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 3/8] boot/optee-os: add support to build with python-cryptography
Date: Sat, 19 Mar 2022 10:17:49 +0100	[thread overview]
Message-ID: <20220319101749.265ebceb@windsurf> (raw)
In-Reply-To: <20220318223221.GS283544@scaer>

On Fri, 18 Mar 2022 23:32:21 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> > diff --git a/boot/optee-os/Config.in b/boot/optee-os/Config.in
> > index ea16550b72..02b5d7c86f 100644
> > --- a/boot/optee-os/Config.in
> > +++ b/boot/optee-os/Config.in
> > @@ -1,6 +1,7 @@
> >  config BR2_TARGET_OPTEE_OS
> >  	bool "optee_os"
> >  	depends on BR2_ARM_CPU_ARMV8A || BR2_ARM_CPU_ARMV7A
> > +	depends on BR2_PACKAGE_HOST_RUSTC_ARCH_SUPPORTS  
> 
> That's wrong: 3.15.0 still does not need host-python-cryptography.
> 
> Furthermore, even after we bump to 3.16.0, since we can choose an
> arbitrary git tree at an arbitrary commit, it is still possible to
> point to a version of optee-os that does not require it either.
> 
> So, that dependency only really belongs...
> 
> >  	help
> >  	  OP-TEE OS provides the secure world boot image and the trust
> >  	  application development kit of the OP-TEE project. OP-TEE OS
> > @@ -61,6 +62,14 @@ config BR2_TARGET_OPTEE_OS_NEEDS_DTC
> >  	  Select this option if your OP-TEE OS platform configuration
> >  	  requires the Device Tree compiler to be available.
> >  
> > +config BR2_TARGET_OPTEE_OS_NEEDS_PYTHON_CRYPTOGRAPHY
> > +	bool "OP-TEE OS needs host-python-cryptography"  
> 
> ... here.

Yes and no. Because as soon as the BR2_TARGET_OPTEE_OS_LATEST gets
bumped to 3.16.0, then our default selection for OP-TEE (unless you
chose a custom Git version) will require python-cryptography. So to
keep things simple, I asked Clément to add this dependency to the
whole package.

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:[~2022-03-19  9:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 13:24 [Buildroot] [PATCH v5 0/8] boot/optee-os: support new optee-os 3.16.0 build dependencies Clément Léger via buildroot
2022-03-18 13:24 ` [Buildroot] [PATCH v5 1/8] package/pkg-generic: host variant inherits target download settings Clément Léger via buildroot
2022-03-18 22:33   ` Yann E. MORIN
2022-03-18 13:24 ` [Buildroot] [PATCH v5 2/8] package/python-cryptography: enable host package Clément Léger via buildroot
2022-03-18 22:32   ` Yann E. MORIN
2022-03-18 13:24 ` [Buildroot] [PATCH v5 3/8] boot/optee-os: add support to build with python-cryptography Clément Léger via buildroot
2022-03-18 22:32   ` Yann E. MORIN
2022-03-19  9:17     ` Thomas Petazzoni via buildroot [this message]
2022-03-19  9:46       ` Yann E. MORIN
2022-03-18 13:24 ` [Buildroot] [PATCH v5 4/8] boot/optee-os: bump to version 3.16.0 Clément Léger via buildroot
2022-03-18 22:40   ` Yann E. MORIN
2022-03-21  7:46     ` Clément Léger via buildroot
2022-03-18 13:24 ` [Buildroot] [PATCH v5 5/8] package/optee-test: " Clément Léger via buildroot
2022-03-18 13:24 ` [Buildroot] [PATCH v5 6/8] package/optee-examples: " Clément Léger via buildroot
2022-03-18 13:24 ` [Buildroot] [PATCH v5 7/8] package/optee-client: " Clément Léger via buildroot
2022-03-18 13:24 ` [Buildroot] [PATCH v5 8/8] package/optee-benchmark: " Clément Léger via buildroot
2022-03-18 22:46 ` [Buildroot] [PATCH v5 0/8] boot/optee-os: support new optee-os 3.16.0 build dependencies Yann E. MORIN

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=20220319101749.265ebceb@windsurf \
    --to=buildroot@buildroot.org \
    --cc=clement.leger@bootlin.com \
    --cc=etienne.carriere@linaro.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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