From: Christian Stewart via buildroot <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Christian Stewart <christian@paral.in>,
Anisse Astier <anisse@astier.eu>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: [Buildroot] [PATCH 2/2] package/runc: fix typo of toolchain in config.in
Date: Fri, 1 Oct 2021 15:29:52 -0700 [thread overview]
Message-ID: <20211001222952.670649-2-christian@paral.in> (raw)
In-Reply-To: <20211001222952.670649-1-christian@paral.in>
BR2_TOOLCHAN_USES_UCLIBC -> BR2_TOOLCHAIN_USES_UCLIBC
Signed-off-by: Christian Stewart <christian@paral.in>
---
package/runc/Config.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/runc/Config.in b/package/runc/Config.in
index f181ee334f..66203896a8 100644
--- a/package/runc/Config.in
+++ b/package/runc/Config.in
@@ -13,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_TOOLCHAN_USES_UCLIBC
+ depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_TOOLCHAIN_USES_UCLIBC
--
2.33.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-01 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 22:29 [Buildroot] [PATCH 1/2] package/lxc: fix typo of toolchain in config.in Christian Stewart via buildroot
2021-10-01 22:29 ` Christian Stewart via buildroot [this message]
2021-10-03 7:53 ` [Buildroot] [PATCH 2/2] package/runc: " Yann E. MORIN
2021-10-06 14:38 ` Peter Korsgaard
2021-10-03 7:53 ` [Buildroot] [PATCH 1/2] package/lxc: " Yann E. MORIN
2021-10-06 14:37 ` Peter Korsgaard
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=20211001222952.670649-2-christian@paral.in \
--to=buildroot@buildroot.org \
--cc=anisse@astier.eu \
--cc=christian@paral.in \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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