From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: kory.maincent@bootlin.com,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Asaf Kahlon <asafka7@gmail.com>,
Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] package/python-pillow: fix host package build
Date: Sun, 17 Jul 2022 18:47:49 +0200 [thread overview]
Message-ID: <20220717184749.13a817bf@windsurf> (raw)
In-Reply-To: <20220717182632.32e8d732@windsurf>
On Sun, 17 Jul 2022 18:26:32 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> That being said, grepping through the optee_os code from ST, I no
> longer see where python-pillow is used. I've started a test build to
> check this (but I'm pretty sure it was needed at some point, as I
> looked into this with Köry).
Seems like this whole python-pillow dance is in fact no longer
needed... at least I can build the latest OPTEE-OS from ST without
host-python-pillow installed (in a clean, minimal Ubuntu Docker
container).
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
next prev parent reply other threads:[~2022-07-17 16:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 11:58 [Buildroot] [PATCH] package/python-pillow: fix host package build Thomas Petazzoni via buildroot
2022-07-17 9:20 ` Yann E. MORIN
2022-07-17 16:26 ` Thomas Petazzoni via buildroot
2022-07-17 16:47 ` Thomas Petazzoni via buildroot [this message]
2022-07-17 18:05 ` Yann E. MORIN
2022-08-10 12:43 ` Peter Korsgaard
2022-08-29 9:07 ` Köry Maincent via buildroot
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=20220717184749.13a817bf@windsurf \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=asafka7@gmail.com \
--cc=kory.maincent@bootlin.com \
--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 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.