From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] configs/imx6-sabresd: bump U-Boot and kernel
Date: Mon, 30 May 2022 22:18:45 +0200 [thread overview]
Message-ID: <20220530221845.009ef9d6@windsurf> (raw)
In-Reply-To: <CAEyMn7ZADNXiVpg2=AL4OrsJ7=ywmp0NmkX37uW72X5D8pFy0Q@mail.gmail.com>
On Fri, 27 May 2022 12:24:09 +0200
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> Hi Fabio,
>
> Am Mi., 25. Mai 2022 um 00:00 Uhr schrieb Fabio Estevam <festevam@gmail.com>:
> >
> > Bump U-Boot to 2022.04 and kernel to 5.15.41 version.
>
> Just to let you know: U-Boot will need gnutls.h on host since 2022.04.
> Thus some additional host dependencies are required. This will be
> fixed in the patch series I provided [1]
This is not true: the U-Boot configuration used for this board does not
build the mkeficapsule tool, so host-gnutls is not needed. I just build
tested in a Docker container which doesn't have gnutls-dev installed,
and it builds fine, and the U-Boot configuration has
CONFIG_TOOLS_MKEFICAPSULE disabled.
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 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:00 [Buildroot] [PATCH] configs/imx6-sabresd: bump U-Boot and kernel Fabio Estevam
2022-05-27 10:24 ` Heiko Thiery
2022-05-30 20:18 ` Thomas Petazzoni via buildroot [this message]
2022-05-30 20:18 ` Thomas Petazzoni via buildroot
-- strict thread matches above, loose matches on Subject: below --
2022-01-04 20:25 [Buildroot] [PATCH] configs/imx6-sabresd: Bump " Fabio Estevam
2018-06-26 22:11 Fabio Estevam
2018-06-28 19:15 ` Thomas Petazzoni
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=20220530221845.009ef9d6@windsurf \
--to=buildroot@buildroot.org \
--cc=festevam@gmail.com \
--cc=heiko.thiery@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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