From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Revert "libiio: Disable IIOD on Blackfin"
Date: Fri, 3 Nov 2017 11:30:33 +0100 [thread overview]
Message-ID: <20171103103034.24937-1-s.martin49@gmail.com> (raw)
This reverts commit 53996bee433f09a91b12aa53b2be0f7d22c0acbe.
Commit 93a86b4dec9e73fbe0e186cdde8fb04a36a44762 fixes accept4 support
in uclibc on Blackfin, so re-enable iiod on this target.
Cc: Paul Cercueil <paul.cercueil@analog.com>
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
---
package/libiio/Config.in | 5 -----
1 file changed, 5 deletions(-)
diff --git a/package/libiio/Config.in b/package/libiio/Config.in
index baa163126a..b58ac7fdb3 100644
--- a/package/libiio/Config.in
+++ b/package/libiio/Config.in
@@ -53,7 +53,6 @@ config BR2_PACKAGE_LIBIIO_IIOD
bool "IIO Daemon"
default y
depends on BR2_TOOLCHAIN_HAS_THREADS
- depends on !BR2_bfin
select BR2_PACKAGE_LIBIIO_LOCAL_BACKEND
help
Install the IIO Daemon.
@@ -74,10 +73,6 @@ comment "USB support in the IIO Daemon requires libaio, headers >= 3.18"
comment "IIO Daemon needs a toolchain w/ threads"
depends on !BR2_TOOLCHAIN_HAS_THREADS
- depends on !BR2_bfin
-
-comment "IIO Daemon is not yet available on Blackfin"
- depends on BR2_bfin
config BR2_PACKAGE_LIBIIO_TESTS
bool "Install test programs"
--
2.15.0
next reply other threads:[~2017-11-03 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 10:30 Samuel Martin [this message]
2017-11-03 10:30 ` [Buildroot] [PATCH 2/2] package/ussp-push: add patches fixing the build Samuel Martin
2017-11-03 21:00 ` [Buildroot] [PATCH 1/2] Revert "libiio: Disable IIOD on Blackfin" 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=20171103103034.24937-1-s.martin49@gmail.com \
--to=s.martin49@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