From: Paul-Erwan Rio <paulerwan.rio@gmail.com>
To: u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>,
Paul-Erwan Rio <paulerwan.rio@gmail.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Andre Przywara <andre.przywara@arm.com>,
Fabio Estevam <festevam@denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Jan Kiszka <jan.kiszka@siemens.com>,
Mamta Shukla <mamta.shukla@leica-geosystems.com>,
Marek Behun <kabel@kernel.org>,
Mark Kettenis <kettenis@openbsd.org>,
Mikhail Ilin <ilin.mikhail.ol@gmail.com>,
Pali Rohar <pali@kernel.org>,
Philippe Reynes <philippe.reynes@softathome.com>,
Sean Anderson <sean.anderson@seco.com>,
Stefan Eichenberger <eichest@gmail.com>,
Stefan Roese <sr@denx.de>,
Steven Lawrance <steven.lawrance@softathome.com>,
Thomas Haemmerle <thomas.haemmerle@leica-geosystems.com>
Subject: [PATCH v1 0/2] Fix host tools build without LIBCRYPTO support
Date: Sat, 21 Jan 2023 16:47:40 +0100 [thread overview]
Message-ID: <20230121154743.667253-1-paulerwan.rio@gmail.com> (raw)
A target-independent configuration exists to enable/disable crypto feature
when building the host tools. But the crypto-free build is broken.
Paul-Erwan Rio (2):
tools: kwbimage: disable secure boot build without LIBCRYPTO support
tools: fix build without LIBCRYPTO support
include/image.h | 2 +-
tools/Kconfig | 1 +
tools/fit_image.c | 2 +-
tools/image-host.c | 2 ++
tools/kwbimage.c | 18 ++++++++++++++++++
tools/mkimage.c | 5 +++--
6 files changed, 26 insertions(+), 4 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-21 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 15:47 Paul-Erwan Rio [this message]
2023-01-21 15:47 ` [PATCH v1 1/2] tools: kwbimage: disable secure boot build without LIBCRYPTO support Paul-Erwan Rio
2023-01-21 15:56 ` Pali Rohar
2023-01-21 16:08 ` Paul-Erwan RIO
2023-01-21 16:21 ` Pali Rohar
2023-01-21 16:31 ` Paul-Erwan RIO
2023-01-21 16:35 ` Pali Rohar
2023-01-21 16:40 ` Paul-Erwan RIO
2023-01-21 15:47 ` [PATCH v1 2/2] tools: fix " Paul-Erwan Rio
2023-01-23 18:50 ` Simon Glass
2023-12-13 15:38 ` Alexander Dahl
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=20230121154743.667253-1-paulerwan.rio@gmail.com \
--to=paulerwan.rio@gmail.com \
--cc=andre.przywara@arm.com \
--cc=eichest@gmail.com \
--cc=festevam@denx.de \
--cc=ilin.mikhail.ol@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kabel@kernel.org \
--cc=kettenis@openbsd.org \
--cc=mamta.shukla@leica-geosystems.com \
--cc=pali@kernel.org \
--cc=philippe.reynes@softathome.com \
--cc=sean.anderson@seco.com \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=steven.lawrance@softathome.com \
--cc=takahiro.akashi@linaro.org \
--cc=thomas.haemmerle@leica-geosystems.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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.