From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Julien Olivain <ju.o@free.fr>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/ola: ftdidmx needs gcc >= 4.9
Date: Sat, 13 Aug 2022 10:46:59 +0200 [thread overview]
Message-ID: <20220813084659.696492-1-fontaine.fabrice@gmail.com> (raw)
Fix the following build failure raised since re-introduction of the
package in commit 16ff948444c3978d63f483344a3d92d994c64312:
Makefile:575: *** libusb is in the dependency chain of libftdi1 that has added it to its _DEPENDENCIES variable without selecting it or depending on it from Config.in. Stop.
Fixes:
- http://autobuild.buildroot.org/results/f65baf4dd4c9a313745cdb9aefad2eae7a295469
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/ola/Config.in | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/package/ola/Config.in b/package/ola/Config.in
index cfca09a936..701083b5d3 100644
--- a/package/ola/Config.in
+++ b/package/ola/Config.in
@@ -86,10 +86,14 @@ config BR2_PACKAGE_OLA_PLUGIN_ESPNET
config BR2_PACKAGE_OLA_PLUGIN_FTDIDMX
bool "ftdidmx"
+ depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 # libftdi1 -> libusb
select BR2_PACKAGE_LIBFTDI1
help
Build FTDI USB DMX plugin for OLA.
+comment "ftdidmx needs a toolchain w/ gcc >= 4.9"
+ depends on !BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
+
config BR2_PACKAGE_OLA_PLUGIN_GPIO
bool "GPIO"
help
--
2.35.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-08-13 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 8:46 Fabrice Fontaine [this message]
2022-08-14 20:56 ` [Buildroot] [PATCH 1/1] package/ola: ftdidmx needs gcc >= 4.9 Yann E. MORIN
2022-09-16 10:13 ` 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=20220813084659.696492-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.