From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Buildroot List <buildroot@buildroot.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Christian Stewart <christian@aperture.us>
Subject: [Buildroot] [PATCH] package/crun: allow building with uClibc
Date: Sat, 29 Jul 2023 23:21:58 +0200 [thread overview]
Message-ID: <20230729212159.403148-1-thomas.petazzoni@bootlin.com> (raw)
uClibc now provides fexecve(), so crun can build just fine with
uClibc. However, argp-standalone is needed, just like it was needed
for musl.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
package/crun/Config.in | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/package/crun/Config.in b/package/crun/Config.in
index 45c86f0655..1b69034459 100644
--- a/package/crun/Config.in
+++ b/package/crun/Config.in
@@ -1,8 +1,7 @@
config BR2_PACKAGE_CRUN
bool "crun"
- depends on !BR2_TOOLCHAIN_USES_UCLIBC # no fexecve
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # C11/stdatomic.h
- select BR2_PACKAGE_ARGP_STANDALONE if BR2_TOOLCHAIN_USES_MUSL
+ select BR2_PACKAGE_ARGP_STANDALONE if !BR2_TOOLCHAIN_USES_GLIBC
select BR2_PACKAGE_YAJL # libocispec
help
crun is a fast and low-memory OCI Container Runtime in C.
--
2.41.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-07-29 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 21:21 Thomas Petazzoni via buildroot [this message]
2023-07-31 2:44 ` [Buildroot] [PATCH] package/crun: allow building with uClibc Christian Stewart via buildroot
2023-08-06 14:28 ` Thomas Petazzoni via buildroot
2023-08-11 20:06 ` Arnout Vandecappelle via buildroot
2023-08-11 22:26 ` 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=20230729212159.403148-1-thomas.petazzoni@bootlin.com \
--to=buildroot@buildroot.org \
--cc=christian@aperture.us \
--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