From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] directfb: depends on NPTL threading
Date: Sat, 9 Jul 2016 00:21:29 +0200 [thread overview]
Message-ID: <20160708222129.GA22796@waldemar-brodkorb.de> (raw)
Fixes following autobuild failure:
http://autobuild.buildroot.net/results/162db0d62075a16c7abae1229676e2cdb29fe953/
Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
v1 -> v2:
- rather adding an experimental patch without runtime testing for
an unmaintained software, we depend on NPTL as discussed with
Thomas Petazzoni on IRC
---
package/directfb/Config.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/directfb/Config.in b/package/directfb/Config.in
index f0bcaaa..f38f051 100644
--- a/package/directfb/Config.in
+++ b/package/directfb/Config.in
@@ -1,6 +1,6 @@
config BR2_PACKAGE_DIRECTFB
bool "directfb"
- depends on BR2_TOOLCHAIN_HAS_THREADS
+ depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
depends on BR2_INSTALL_LIBSTDCPP
depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_5
depends on !BR2_TOOLCHAIN_USES_MUSL # sigval_t issue
--
2.1.4
next reply other threads:[~2016-07-08 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 22:21 Waldemar Brodkorb [this message]
2016-07-16 15:36 ` [Buildroot] [PATCH v2] directfb: depends on NPTL threading Romain Naour
2016-07-17 13:08 ` Thomas Petazzoni
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=20160708222129.GA22796@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox