public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Alexander Dahl <ada@thorsis.com>
Cc: u-boot@lists.denx.de, "Marek Vasut" <marex@denx.de>,
	"Pali Rohár" <pali@kernel.org>,
	"Philippe Reynes" <philippe.reynes@softathome.com>
Subject: Re: Build with CONFIG_TOOLS_LIBCRYPTO disabled is broken
Date: Wed, 27 Jul 2022 09:08:56 -0400	[thread overview]
Message-ID: <20220727130856.GU1146598@bill-the-cat> (raw)
In-Reply-To: <1884029.XjOfZupGQm@ada>

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

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.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2022-07-27 13:09 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 [this message]
2022-08-02 13:10   ` 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=20220727130856.GU1146598@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=ada@thorsis.com \
    --cc=marex@denx.de \
    --cc=pali@kernel.org \
    --cc=philippe.reynes@softathome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox