From: Fabio Estevam <festevam@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: marex@nabladev.com, Fabio Estevam <festevam@nabladev.com>
Subject: [PATCH 1/2] gnutls: Enable p11-kit by default
Date: Thu, 16 Jul 2026 09:22:17 -0300 [thread overview]
Message-ID: <20260716122219.569673-1-festevam@gmail.com> (raw)
From: Fabio Estevam <festevam@nabladev.com>
U-Boot 2026.07 enables the mkeficapsule tool by default. During its
build, mkeficapsule links against libgnutls and requires PKCS#11
symbols such as gnutls_pkcs11_init().
Commit e9f12f64279c ("gnutls: Add p11-kit for native builds") enabled
p11-kit only for gnutls-native. However, this is not sufficient to
build u-boot-tools, which still fails to link mkeficapsule with
undefined references to the PKCS#11 API.
Enable p11-kit in the default PACKAGECONFIG so that the required
symbols are available and u-boot-tools builds successfully.
Signed-off-by: Fabio Estevam <festevam@nabladev.com>
---
meta/recipes-support/gnutls/gnutls_3.8.13.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/recipes-support/gnutls/gnutls_3.8.13.bb b/meta/recipes-support/gnutls/gnutls_3.8.13.bb
index 943864d4ba..ce9f2b16ff 100644
--- a/meta/recipes-support/gnutls/gnutls_3.8.13.bb
+++ b/meta/recipes-support/gnutls/gnutls_3.8.13.bb
@@ -31,8 +31,7 @@ SRC_URI[sha256sum] = "ffed8ec1bf09c2426d4f14aae377de4753b53e537d685e604e99a8b16c
inherit autotools texinfo pkgconfig gettext lib_package gtk-doc ptest
-PACKAGECONFIG ??= "libidn libtasn1 ${@bb.utils.filter('DISTRO_FEATURES', 'seccomp', d)}"
-PACKAGECONFIG:append:class-native = " p11-kit"
+PACKAGECONFIG ??= "libidn libtasn1 p11-kit ${@bb.utils.filter('DISTRO_FEATURES', 'seccomp', d)}"
# You must also have CONFIG_SECCOMP enabled in the kernel for
# seccomp to work.
--
2.43.0
next reply other threads:[~2026-07-16 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 12:22 Fabio Estevam [this message]
2026-07-16 12:22 ` [PATCH 2/2] u-boot: upgrade 2026.04 -> 2026.07 Fabio Estevam
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=20260716122219.569673-1-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=festevam@nabladev.com \
--cc=marex@nabladev.com \
--cc=openembedded-core@lists.openembedded.org \
/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