From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/openocd: select libusb when selecting libusb-compat
Date: Fri, 1 Jan 2016 17:01:06 +0100 [thread overview]
Message-ID: <1451664066-6127-1-git-send-email-romain.naour@gmail.com> (raw)
libusb-compat depends on libusb package, so we need to select
libusb package at the same time as libusb-compat to avoid an
unmet dependency.
Since 28f67899e54f15c6e48484ea2976c3e431756bcb, the build
stop if a package build is trigged at Makefile level without
being selected at Config.in level.
This is the case here with BR2_PACKAGE_OPENOCD_USBPROG which
select BR2_PACKAGE_LIBUSB_COMPAT without selecting
BR2_PACKAGE_LIBUSB.
Fixes:
http://autobuild.buildroot.net/results/b4a/b4a8c54eed6bf75ab8ade0653953d19792155727/
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
package/openocd/Config.in | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/package/openocd/Config.in b/package/openocd/Config.in
index d84aac1..a35bd27 100644
--- a/package/openocd/Config.in
+++ b/package/openocd/Config.in
@@ -84,6 +84,7 @@ config BR2_PACKAGE_OPENOCD_AICE
config BR2_PACKAGE_OPENOCD_VSLLINK
bool "Versaloon-Link JTAG Programmer"
+ select BR2_PACKAGE_LIBUSB
select BR2_PACKAGE_LIBUSB_COMPAT
depends on BR2_TOOLCHAIN_HAS_THREADS # libusb-compat -> libusb
help
@@ -92,6 +93,7 @@ config BR2_PACKAGE_OPENOCD_VSLLINK
config BR2_PACKAGE_OPENOCD_USBPROG
bool "USBProg JTAG Programmer"
+ select BR2_PACKAGE_LIBUSB
select BR2_PACKAGE_LIBUSB_COMPAT
depends on BR2_TOOLCHAIN_HAS_THREADS # libusb-compat -> libusb
help
@@ -100,6 +102,7 @@ config BR2_PACKAGE_OPENOCD_USBPROG
config BR2_PACKAGE_OPENOCD_RLINK
bool "Raisonance RLink JTAG Programmer"
+ select BR2_PACKAGE_LIBUSB
select BR2_PACKAGE_LIBUSB_COMPAT
depends on BR2_TOOLCHAIN_HAS_THREADS # libusb-compat -> libusb
help
@@ -108,6 +111,7 @@ config BR2_PACKAGE_OPENOCD_RLINK
config BR2_PACKAGE_OPENOCD_ARMEW
bool "Olimex ARM-JTAG-EW Programmer"
+ select BR2_PACKAGE_LIBUSB
select BR2_PACKAGE_LIBUSB_COMPAT
depends on BR2_TOOLCHAIN_HAS_THREADS # libusb-compat -> libusb
help
@@ -186,6 +190,7 @@ config BR2_PACKAGE_OPENOCD_PRESTO
config BR2_PACKAGE_OPENOCD_OPENJTAG
bool "OpenJTAG Programmer"
select BR2_PACKAGE_LIBFTDI1
+ select BR2_PACKAGE_LIBUSB
select BR2_PACKAGE_LIBUSB_COMPAT # needs usb.h
depends on BR2_TOOLCHAIN_HAS_THREADS # libftdi -> libusb
depends on BR2_ARCH_HAS_ATOMICS
--
2.4.3
next reply other threads:[~2016-01-01 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 16:01 Romain Naour [this message]
2016-01-01 16:07 ` [Buildroot] [PATCH 1/1] package/openocd: select libusb when selecting libusb-compat Yann E. MORIN
2016-01-01 18:56 ` Peter Korsgaard
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=1451664066-6127-1-git-send-email-romain.naour@gmail.com \
--to=romain.naour@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