From: Alexander Dahl <ada@thorsis.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Marek Vasut" <marex@denx.de>,
"Pali Rohár" <pali@kernel.org>,
"Philippe Reynes" <philippe.reynes@softathome.com>,
"Alexander Dahl" <ada@thorsis.com>
Subject: Re: Build with CONFIG_TOOLS_LIBCRYPTO disabled is broken
Date: Tue, 02 Aug 2022 15:10:13 +0200 [thread overview]
Message-ID: <3706927.dslp0D23Aq@ada> (raw)
In-Reply-To: <20220727130856.GU1146598@bill-the-cat>
Hello everyone,
Am Mittwoch, 27. Juli 2022, 15:08:56 CEST schrieb Tom Rini:
> On Tue, Jul 26, 2022 at 10:27:01AM +0200, Alexander Dahl wrote:
> > Hei hei,
> >
> > once again I tried building U-Boot with CONFIG_TOOLS_LIBCRYPTO disabled
> > and
> > with no libssl-dev installed on the build machine. It does not work.
> >
> > Even porting the patch disabling the build with kwbimage (see links below)
> > does not help anymore, because since commit 6e052d1cbafb ("mkimage: add
> > public key for image pre-load stage") there's a new hard dependency on
> > host openssl in tools/image-host.c and the corresponding kconfig symbol
> > CONFIG_TOOLS_FIT can not be disabled through menuconfig.
> >
> > Just read those discussions again, but not sure what can be done to
> > proceed
> > here? Can I help somehow?
>
> I think we need a new patch that guards the new functions / calls under
> CONFIG_TOOLS_LIBCRYPTO and then a new CI job that removes libssl-dev
> before building tools-only so we don't re-introduce the problem is what
> we need to move forward here.
Apart from that kwbimage stuff, the changeset 6e052d1cbafb mentioned above
touches the following files:
- include/image.h
- tools/fit_image.c
- tools/image-host.c
Conditional building for CONFIG_TOOLS_LIBCRYPTO can currently only be found in
tools/Makefile (not through #ifdefs in header or source files).
I'm not sure if fit_image.o and image-host.o should be moved away from
FIT_OBJS-y to something else, though. This probably requires a better
understanding of those objects than I have. :-/
Greets
Alex
prev parent reply other threads:[~2022-08-02 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 8:27 Build with CONFIG_TOOLS_LIBCRYPTO disabled is broken Alexander Dahl
2022-07-26 19:53 ` Simon Glass
2022-07-27 13:08 ` Tom Rini
2022-08-02 13:10 ` Alexander Dahl [this message]
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=3706927.dslp0D23Aq@ada \
--to=ada@thorsis.com \
--cc=marex@denx.de \
--cc=pali@kernel.org \
--cc=philippe.reynes@softathome.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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.