From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ussp-push: add bluez5_utils support
Date: Sat, 11 Jan 2020 15:32:09 +0100 [thread overview]
Message-ID: <20200111153209.2a6b57d6@windsurf> (raw)
In-Reply-To: <20200111092101.419186-1-fontaine.fabrice@gmail.com>
On Sat, 11 Jan 2020 10:21:01 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/ussp-push/Config.in | 2 +-
> package/ussp-push/ussp-push.mk | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/package/ussp-push/Config.in b/package/ussp-push/Config.in
> index aefec85a20..d0ab577609 100644
> --- a/package/ussp-push/Config.in
> +++ b/package/ussp-push/Config.in
> @@ -5,7 +5,7 @@ config BR2_PACKAGE_USSP_PUSH
> depends on BR2_TOOLCHAIN_HAS_THREADS # dbus, alsa-lib, libglib2
> depends on BR2_USE_MMU # dbus
> select BR2_PACKAGE_OPENOBEX
> - select BR2_PACKAGE_BLUEZ_UTILS
> + select BR2_PACKAGE_BLUEZ_UTILS if !BR2_PACKAGE_BLUEZ5_UTILS
Doing this causes a Kconfig circular dependency:
package/bluez_utils/Config.in:1:error: recursive dependency detected!
package/bluez_utils/Config.in:1: symbol BR2_PACKAGE_BLUEZ_UTILS is selected by BR2_PACKAGE_BLUEZ5_UTILS
package/bluez5_utils/Config.in:1: symbol BR2_PACKAGE_BLUEZ5_UTILS is selected by BR2_PACKAGE_BLUEZ_ALSA
package/bluez-alsa/Config.in:1: symbol BR2_PACKAGE_BLUEZ_ALSA depends on BR2_PACKAGE_BLUEZ_UTILS
This problem also affects your cwiid and sconeserver patches.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-01-11 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 9:21 [Buildroot] [PATCH 1/1] package/ussp-push: add bluez5_utils support Fabrice Fontaine
2020-01-11 14:32 ` Thomas Petazzoni [this message]
2020-01-11 14:37 ` Fabrice Fontaine
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=20200111153209.2a6b57d6@windsurf \
--to=thomas.petazzoni@bootlin.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 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.