Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joris Lijssens <joris.lijssens@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] rabbitmq-c: needs a toolchain with posix_spawn support
Date: Thu, 14 Jan 2016 11:51:33 +0100	[thread overview]
Message-ID: <1452768693-1078-1-git-send-email-joris.lijssens@gmail.com> (raw)

Fixes:
http://autobuild.buildroot.net/results/a6c3e79c61c5a535970d03bf37b068349f766a7f/
Signed-off-by: Joris Lijssens <joris.lijssens@gmail.com>
---
 package/rabbitmq-c/Config.in | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/package/rabbitmq-c/Config.in b/package/rabbitmq-c/Config.in
index b330c90..0d08233 100644
--- a/package/rabbitmq-c/Config.in
+++ b/package/rabbitmq-c/Config.in
@@ -1,6 +1,9 @@
 config BR2_PACKAGE_RABBITMQ_C
 	bool "rabbitmq-c"
 	depends on BR2_TOOLCHAIN_HAS_THREADS
+	# too old uClibc, not providing posix_spawn functions
+	# http://autobuild.buildroot.net/results/a6c3e79c61c5a535970d03bf37b068349f766a7f/
+	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX
 	help
 	  This is a C-language AMQP client library for use with v2.0+
 	  of the RabbitMQ broker.
@@ -9,3 +12,4 @@ config BR2_PACKAGE_RABBITMQ_C
 
 comment "rabbitmq-c needs a toolchain w/ threads"
 	depends on !BR2_TOOLCHAIN_HAS_THREADS
+	depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX
-- 
1.8.3.1

             reply	other threads:[~2016-01-14 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 10:51 Joris Lijssens [this message]
2016-01-14 10:59 ` [Buildroot] [PATCH v3] rabbitmq-c: needs a toolchain with posix_spawn support Thomas Petazzoni
2016-01-14 11:59   ` Joris Lijssens

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=1452768693-1078-1-git-send-email-joris.lijssens@gmail.com \
    --to=joris.lijssens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox