From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org, Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH] package/runc: enable uClibc support
Date: Tue, 1 Sep 2026 22:51:27 +0200 [thread overview]
Message-ID: <apc5egLCDDm39inI@windsurf> (raw)
In-Reply-To: <aoG3tN3r2SnRX0el@waldemar-brodkorb.de>
Hello Waldemar,
Thanks for your patch!
On Sun, Aug 16, 2026 at 03:14:28PM +0200, Waldemar Brodkorb wrote:
> 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"
You need to update this comment, to drop "glibc or musl". I had done
that locally, because it was trivial.
But the less trivial thing that you need to do is look at the reverse
dependencies of runc:
package/containerd/Config.in: select BR2_PACKAGE_RUNC if !BR2_PACKAGE_CRUN # runtime dependency
package/podman/Config.in: select BR2_PACKAGE_RUNC if !BR2_PACKAGE_CRUN # runtime
containerd has:
depends on !BR2_TOOLCHAIN_USES_UCLIBC # runc
which is no longer correct since runc no longer depends on !uclibc. So
either this dependency can be dropped, or its comment needs to be
updated to explain why containerd still doesn't work with uclibc.
Regarding podman, it's even weirder because it doesn't have this
dependency.. But I guess that's OK because podman needs rust, and rust
is only available for glibc and musl configurations. That's why we
didn't see any issue there.
Still, the containerd case needs to be looked at. Can you check this?
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
prev parent reply other threads:[~2026-09-01 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 13:14 [Buildroot] [PATCH] package/runc: enable uClibc support Waldemar Brodkorb
2026-09-01 20:51 ` Thomas Petazzoni 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=apc5egLCDDm39inI@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.