From: Alexander Shirokov <shirokovalexs@gmail.com>
To: buildroot@buildroot.org
Cc: thomas.petazzoni@bootlin.com,
Alexander Shirokov <shirokovalexs@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/nnn: add BR2_TOOLCHAIN_HAS_THREADS dependency
Date: Sat, 19 Sep 2026 18:35:56 +0200 [thread overview]
Message-ID: <20260919163604.897135-1-shirokovalexs@gmail.com> (raw)
nnn links against pthread. Specify the dependency to avoid
unexpected build failures on toolchains lacking thread support (e.g.
br-arm-full-nothread).
Signed-off-by: Alexander Shirokov <shirokovalexs@gmail.com>
---
package/nnn/Config.in | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/package/nnn/Config.in b/package/nnn/Config.in
index 64cfa8e0a5..555ab864d9 100644
--- a/package/nnn/Config.in
+++ b/package/nnn/Config.in
@@ -1,6 +1,7 @@
config BR2_PACKAGE_NNN
bool "nnn"
depends on BR2_USE_MMU # fork
+ depends on BR2_TOOLCHAIN_HAS_THREADS
# Building nnn without widechar/UTF support is theoretically
# possible, but in practice it leads to unstable builds.
# That’s why the WCHAR dependency is here.
@@ -15,6 +16,6 @@ config BR2_PACKAGE_NNN
https://github.com/jarun/nnn
-comment "nnn needs a toolchain with wchar"
+comment "nnn needs a toolchain with wchar, threads"
depends on BR2_USE_MMU # fork
- depends on !BR2_USE_WCHAR
+ depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
--
2.55.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-09-19 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 16:35 Alexander Shirokov [this message]
2026-09-20 11:28 ` [Buildroot] [PATCH 1/1] package/nnn: add BR2_TOOLCHAIN_HAS_THREADS dependency Thomas Petazzoni via buildroot
2026-09-22 13:18 ` [Buildroot] [v2 " Alexander Shirokov
2026-10-10 17:25 ` 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=20260919163604.897135-1-shirokovalexs@gmail.com \
--to=shirokovalexs@gmail.com \
--cc=buildroot@buildroot.org \
--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