From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/cwiid: add optional dependency to bluez5_utils
Date: Mon, 6 Mar 2017 09:03:13 +0100 [thread overview]
Message-ID: <20170306090313.6dfadac1@free-electrons.com> (raw)
In-Reply-To: <c592221b-1de8-f298-2628-c346f443c9a2@mind.be>
Hello,
On Mon, 6 Mar 2017 00:37:38 +0100, Arnout Vandecappelle wrote:
> > This causes a 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 depends on BR2_PACKAGE_BLUEZ_UTILS
>
> I think it's just a matter of swapping them:
>
> select BR2_PACKAGE_BLUEZ5_UTILS if !BR2_PACKAGE_BLUEZ_UTILS
Yeah but that one changes the current behavior: if you have a defconfig
with BR2_PACKAGE_CWIID=y, then you have been using bluez_utils, and
your change would move to use bluez5_utils instead.
That being said, I don't know if it matters that much.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-06 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 13:18 [Buildroot] [PATCH 1/2] package/cwiid: bump version Bernd Kuhls
2017-02-19 13:18 ` [Buildroot] [PATCH 2/2] package/cwiid: add optional dependency to bluez5_utils Bernd Kuhls
2017-03-01 21:23 ` Thomas Petazzoni
2017-03-05 23:37 ` Arnout Vandecappelle
2017-03-06 8:03 ` Thomas Petazzoni [this message]
2017-03-06 12:27 ` Arnout Vandecappelle
2017-03-01 21:20 ` [Buildroot] [PATCH 1/2] package/cwiid: bump version Thomas Petazzoni
2017-03-09 22:35 ` Alexandre Belloni
2017-03-10 6:05 ` Bernd Kuhls
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=20170306090313.6dfadac1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.