From: spdawson at gmail.com <spdawson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libusb: disable on avr32
Date: Sat, 17 Nov 2012 19:55:56 +0000 [thread overview]
Message-ID: <1353182156-28906-1-git-send-email-spdawson@gmail.com> (raw)
From: Simon Dawson <spdawson@gmail.com>
For target architecture avr32, the gpsd package fails to build when
libusb is selected. The following autobuild failure illustrates the problem.
http://autobuild.buildroot.net/results/aa3d4763a0e90c995bc8431cf345730ee22e65a1/build-end.log
The issue is that libusb requires timerfd_settime and timerfd_create, but
the underlying syscalls are not implemented on avr32.
This patch disables the libusb package for the avr32 target architecture.
Signed-off-by: Simon Dawson <spdawson@gmail.com>
---
package/libusb/Config.in | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/package/libusb/Config.in b/package/libusb/Config.in
index 2eed3fa..cbaeac6 100644
--- a/package/libusb/Config.in
+++ b/package/libusb/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_LIBUSB
bool "libusb"
+ depends on !BR2_avr32 # timerfd not in uClibc-0.9.31
depends on BR2_TOOLCHAIN_HAS_THREADS
help
Userspace library for accessing USB devices
@@ -7,4 +8,4 @@ config BR2_PACKAGE_LIBUSB
http://libusb.sourceforge.net/
comment "libusb needs a toolchain with thread support"
- depends on !BR2_TOOLCHAIN_HAS_THREADS
+ depends on !BR2_TOOLCHAIN_HAS_THREADS && !BR2_avr32
--
1.7.10.4
next reply other threads:[~2012-11-17 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-17 19:55 spdawson at gmail.com [this message]
2012-11-17 19:58 ` [Buildroot] [PATCH] libusb: disable on avr32 Peter Korsgaard
2012-11-17 20:02 ` Simon Dawson
2012-11-17 20:13 ` Peter Korsgaard
2012-11-17 20:19 ` Simon Dawson
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=1353182156-28906-1-git-send-email-spdawson@gmail.com \
--to=spdawson@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