From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@buildroot.org
Cc: Christian Stewart <christian@aperture.us>
Subject: [Buildroot] [PATCH] package/runc: enable uClibc support
Date: Sun, 16 Aug 2026 15:14:28 +0200 [thread overview]
Message-ID: <aoG3tN3r2SnRX0el@waldemar-brodkorb.de> (raw)
fexecve was added to uClibc in 2019 in commit
858ffad217076227089cc17eb832db0bd1497792.
Runtime tested on a Raspberry PI4 (64 Bit).
System compiled with Bootlin Toolchain.
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
package/runc/Config.in | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/package/runc/Config.in b/package/runc/Config.in
index 73eac72527..e4027fddaa 100644
--- a/package/runc/Config.in
+++ b/package/runc/Config.in
@@ -3,7 +3,6 @@ config BR2_PACKAGE_RUNC
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS
depends on BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
depends on BR2_TOOLCHAIN_HAS_THREADS
- depends on !BR2_TOOLCHAIN_USES_UCLIBC # no fexecve
select BR2_PACKAGE_HOST_GO
help
runC is a CLI tool for spawning and running containers
@@ -14,4 +13,4 @@ config BR2_PACKAGE_RUNC
comment "runc needs a glibc or musl toolchain w/ threads"
depends on BR2_PACKAGE_HOST_GO_TARGET_ARCH_SUPPORTS && \
BR2_PACKAGE_HOST_GO_TARGET_CGO_LINKING_SUPPORTS
- depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_TOOLCHAIN_USES_UCLIBC
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
--
2.47.3
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-08-16 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 13:14 Waldemar Brodkorb [this message]
2026-09-01 20:51 ` [Buildroot] [PATCH] package/runc: enable uClibc support Thomas Petazzoni via buildroot
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=aoG3tN3r2SnRX0el@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
/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