From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: Robin van der Gracht <robin@protonic.nl>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/2] optee-client: version bump 3.5.0 -> 3.11.0
Date: Fri, 08 Jan 2021 11:26:02 +0100 [thread overview]
Message-ID: <9d39fc9763a9b98b7a512c98830b83fbd06a4a35.camel@pengutronix.de> (raw)
In-Reply-To: <20210108100135.GL9321@pengutronix.de>
On Fri, 2021-01-08 at 11:01 +0100, Michael Olbrich wrote:
> On Fri, Jan 08, 2021 at 10:51:43AM +0100, Rouven Czerwinski wrote:
> > On Fri, 2021-01-08 at 09:57 +0100, Michael Olbrich wrote:
> > > On Thu, Dec 17, 2020 at 09:14:53AM +0100, Robin van der Gracht wrote:
> > > > Signed-off-by: Robin van der Gracht <robin@protonic.nl>
> > >
> > > Hmm, shouldn't optee be updated as well?
> > >
> > > Rouven, what do you think?
> >
> > Yep and the tests should be updated as well.
> >
> > For the OP-TEE OS Update you'll need to add checks for the correct
> > python3 module availability within ptxdist as well.
>
> Probably s/HOST_SYSTEM_PYTHON/HOST_SYSTEM_PYTHON3/ right? Or are new
> packages needed?
OP-TEE OS currently requires python3-cryptodome and python3-pyelftools
to build. Same should be true for the TAs build in the test repository,
since they use the same scripts from the ta-devkit.
Regards,
Rouven
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-01-08 10:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 8:14 Robin van der Gracht
2021-01-08 8:57 ` Michael Olbrich
2021-01-08 9:14 ` robin
2021-01-08 9:51 ` Rouven Czerwinski
2021-01-08 10:01 ` Michael Olbrich
2021-01-08 10:26 ` Rouven Czerwinski [this message]
2021-01-08 10:32 ` Michael Olbrich
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=9d39fc9763a9b98b7a512c98830b83fbd06a4a35.camel@pengutronix.de \
--to=r.czerwinski@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=robin@protonic.nl \
/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