U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, pali@kernel.org, mr.nuke.me@gmail.com
Subject: Re: Re: Broken build with disabling OpenSSL crypto
Date: Sun, 10 Oct 2021 13:04:34 +0200	[thread overview]
Message-ID: <4682648.31r3eYUQgx@kista> (raw)
In-Reply-To: <20211007194100.GX31748@bill-the-cat>

Hi!

Dne četrtek, 07. oktober 2021 ob 21:41:00 CEST je Tom Rini napisal(a):
> On Wed, Oct 06, 2021 at 11:27:43PM +0200, Jernej Škrabec wrote:
> 
> > Hi everyone!
> > 
> > Commit cb9faa6f98ae ("tools: Use a single target-independent config to 
enable 
> > OpenSSL") recently introduced option to disable usage of OpenSSL via 
> > CONFIG_TOOLS_LIBCRYPTO. However, just a bit later, another commit 
b4f3cc2c42d9 
> > ("tools: kwbimage: Do not hide usage of secure header under 
> > CONFIG_ARMADA_38X") made U-Boot tools hard dependent on OpenSSL. That 
totally 
> > defeats the purpose of first commit. I suggest that it gets reverted.
> > 
> > I would like disable OpenSSL for my usage, since it gives me troubles when 
> > cross-compiling U-Boot inside LibreELEC build system. It's not needed for 
our 
> > case anyway.
> 
> How hard is it to specify openssl as a dependency for U-Boot, in the
> LibreELEC build system?  I assume openssl is being used in other parts
> of the build anyhow.  Thanks!

Sure, OpenSSL package is present and we fixed issue with pkg-config in the 
meantime (it picked target paths instead for the host). However, that doesn't 
change anything. CONFIG_TOOLS_LIBCRYPTO is still borked and should be either 
fixed or dropped. I prefer first option because OpenSSL dependency can be 
removed and that allows more concurrency (multiple packages are built at the 
same time).

Best regards,
Jernej



      reply	other threads:[~2021-10-10 11:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 21:27 Broken build with disabling OpenSSL crypto Jernej Škrabec
2021-10-06 22:05 ` Alex G.
2021-10-08  9:34   ` Rudi Heitbaum
2021-10-10 11:06   ` Jernej Škrabec
2021-10-11 16:48     ` Alex G.
2021-10-13  5:26   ` Andre Heider
2021-10-15 11:34   ` Pali Rohár
2021-10-15 14:35     ` Alex G.
2021-10-15 20:30       ` Pali Rohár
2021-10-18 14:04         ` Alex G.
2021-10-07 19:41 ` Tom Rini
2021-10-10 11:04   ` Jernej Škrabec [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=4682648.31r3eYUQgx@kista \
    --to=jernej.skrabec@gmail.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=pali@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox