From: Chris Packham <judge.packham@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/coremark-pro: fix build without threads
Date: Mon, 11 Jan 2021 22:13:53 +1300 [thread overview]
Message-ID: <20210111091353.6978-1-judge.packham@gmail.com> (raw)
Coremark-pro requires threads so add a depends on
BR2_TOOLCHAIN_HAS_THREADS.
Fixes:
- http://autobuild.buildroot.net/results/ab574485a7856fcf5cd643c154c44b4bfcb34a97/
Signed-off-by: Chris Packham <judge.packham@gmail.com>
---
| 5 +++++
1 file changed, 5 insertions(+)
--git a/package/coremark-pro/Config.in b/package/coremark-pro/Config.in
index dd6821056c..362826f47b 100644
--- a/package/coremark-pro/Config.in
+++ b/package/coremark-pro/Config.in
@@ -1,8 +1,13 @@
config BR2_PACKAGE_COREMARK_PRO
bool "coremark-pro"
depends on BR2_USE_MMU # perl uses fork()
+ depends on BR2_TOOLCHAIN_HAS_THREADS
select BR2_PACKAGE_PERL
help
CoreMark-PRO is a comprehensive, advanced processor benchmark.
https://www.eembc.org/coremark-pro/
+
+comment "coremark-pro needs a toolchain w/ threads"
+ depends on !BR2_TOOLCHAIN_HAS_THREADS
+ depends on BR2_USE_MMU
--
2.30.0
next reply other threads:[~2021-01-11 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 9:13 Chris Packham [this message]
2021-01-11 21:22 ` [Buildroot] [PATCH] package/coremark-pro: fix build without threads Thomas Petazzoni
2021-01-11 21:34 ` Chris Packham
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=20210111091353.6978-1-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--cc=buildroot@busybox.net \
/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.