From: Tom Rini <trini@konsulko.com>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>
Cc: u-boot@lists.denx.de, pali@kernel.org, mr.nuke.me@gmail.com
Subject: Re: Broken build with disabling OpenSSL crypto
Date: Thu, 7 Oct 2021 15:41:00 -0400 [thread overview]
Message-ID: <20211007194100.GX31748@bill-the-cat> (raw)
In-Reply-To: <18564205.Z0HQFNUZ9R@kista>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
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!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-10-07 19:41 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 [this message]
2021-10-10 11:04 ` Jernej Škrabec
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=20211007194100.GX31748@bill-the-cat \
--to=trini@konsulko.com \
--cc=jernej.skrabec@gmail.com \
--cc=mr.nuke.me@gmail.com \
--cc=pali@kernel.org \
--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.