From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: buildroot@buildroot.org, "Vincent Stehlé" <vincent.stehle@arm.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/uboot-tools: select p11-kit when building target mkeficapsule
Date: Sun, 09 Aug 2026 17:35:02 +0200 [thread overview]
Message-ID: <84e5eabe89e688acbe39d9db223d67ec@free.fr> (raw)
In-Reply-To: <20260809111130.2074795-1-fiona.klute@gmx.de>
On 09/08/2026 13:11, Fiona Klute via buildroot wrote:
> Since upstream commit 0c716a157be460006a4b762625de329b5e36dbf9 (first
> release: v2026.07) mkeficapsule supports PKCS#11 keys, and in turn
> requires GnuTLS with PKCS#11 support.
>
> Without it, building mkeficapsule for the target fails:
>
> HOSTLD tools/mkeficapsule
> /home/fiona/br-test-pkg/bootlin-armv5-uclibc/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/14.3.0/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld:
> tools/mkeficapsule.o: in function `main':
> mkeficapsule.c:(.text.startup+0x530): undefined reference to
> `gnutls_pkcs11_init'
> /home/fiona/br-test-pkg/bootlin-armv5-uclibc/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/14.3.0/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld:
> mkeficapsule.c:(.text.startup+0x544): undefined reference to
> `gnutls_pkcs11_add_provider'
> /home/fiona/br-test-pkg/bootlin-armv5-uclibc/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/14.3.0/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld:
> mkeficapsule.c:(.text.startup+0x5fc): undefined reference to
> `gnutls_pkcs11_obj_list_import_url4'
> /home/fiona/br-test-pkg/bootlin-armv5-uclibc/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/14.3.0/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld:
> mkeficapsule.c:(.text.startup+0x620): undefined reference to
> `gnutls_x509_crt_import_pkcs11'
> /home/fiona/br-test-pkg/bootlin-armv5-uclibc/host/opt/ext-toolchain/bin/../lib/gcc/arm-buildroot-linux-uclibcgnueabi/14.3.0/../../../../arm-buildroot-linux-uclibcgnueabi/bin/ld:
> mkeficapsule.c:(.text.startup+0x1334): undefined reference to
> `gnutls_pkcs11_deinit'
> collect2: error: ld returned 1 exit status
>
> The error can be reproduced using "utils/test-pkg -c" with the
> following config:
>
> BR2_PACKAGE_UBOOT_TOOLS=y
> BR2_PACKAGE_UBOOT_TOOLS_MKEFICAPSULE=y
>
> For host-uboot-tools this was solved in Buildroot commit
> 6597563da7bb359eac57c8fb70e4efc3d6ef4c02 "package/gnutls: add host
> support for pkcs11" by unconditionally enabling PKCS#11 support for
> host-gnutls. For the target a more fine-grained approach is desirable,
> so instead select BR2_PACKAGE_P11_KIT if
> BR2_PACKAGE_UBOOT_TOOLS_MKEFICAPSULE=y and propagate dependencies.
>
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-08-09 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 11:11 [Buildroot] [PATCH 1/1] package/uboot-tools: select p11-kit when building target mkeficapsule Fiona Klute via buildroot
2026-08-09 15:35 ` Julien Olivain via buildroot [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=84e5eabe89e688acbe39d9db223d67ec@free.fr \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=ju.o@free.fr \
--cc=vincent.stehle@arm.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