From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] boot/uboot: bump to 2022.04
Date: Mon, 30 May 2022 21:44:55 +0200 [thread overview]
Message-ID: <20220530214455.7001115d@windsurf> (raw)
In-Reply-To: <20220521123838.2881-5-heiko.thiery@gmail.com>
Hello,
On Sat, 21 May 2022 14:38:44 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> Since U-Boot 2022.04 a host dependency to gnutls is required.
Are you sure this is an unconditional dependency?
When I read tools/Makefile, I see:
HOSTLDLIBS_mkeficapsule += -lgnutls -luuid
hostprogs-$(CONFIG_TOOLS_MKEFICAPSULE) += mkeficapsule
so it's only configurations with CONFIG_TOOLS_MKEFICAPSULE=y that need
host-gnutls.
So unless I'm missing something, the host-gnutls dependency should not
be made a new mandatory dependency, and instead a "U-Boot needs
host-gnutls" option should be added, like
BR2_TARGET_UBOOT_NEEDS_OPENSSL.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-05-30 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 12:38 [Buildroot] [PATCH 0/4] U-Boot bump to 2022.04 Heiko Thiery
2022-05-21 12:38 ` [Buildroot] [PATCH 1/4] package/nettle: add build support for host Heiko Thiery
2022-05-21 12:38 ` [Buildroot] [PATCH 2/4] package/libtasn1: " Heiko Thiery
2022-05-21 12:38 ` [Buildroot] [PATCH 3/4] package/gnutls: " Heiko Thiery
2022-05-21 12:38 ` [Buildroot] [PATCH 4/4] boot/uboot: bump to 2022.04 Heiko Thiery
2022-05-30 19:44 ` Thomas Petazzoni via buildroot [this message]
2022-05-21 12:40 ` [Buildroot] [PATCH 0/4] U-Boot " Heiko Thiery
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=20220530214455.7001115d@windsurf \
--to=buildroot@buildroot.org \
--cc=heiko.thiery@gmail.com \
--cc=matthew.weber@collins.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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