From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/libpcap: fix bluez circular dependency
Date: Mon, 18 Mar 2019 21:56:04 +0100 [thread overview]
Message-ID: <20190318215604.117a03e0@windsurf> (raw)
In-Reply-To: <45321e8446f7e16a4c1d5f4a9b827c5d2e75bdc3.1552849786.git.baruch@tkos.co.il>
On Sun, 17 Mar 2019 21:09:46 +0200
Baruch Siach <baruch@tkos.co.il> wrote:
> The optional bluez_utils dependency of libpcap creates a circular
> dependency:
>
> $ make dbus-show-recursive-depends
>
> Recursion detected for : systemd
> which is a dependency of: dbus
> which is a dependency of: bluez_utils
> which is a dependency of: libpcap
> which is a dependency of: iptables
> which is a dependency of: systemd
> make: *** [package/dbus/dbus.mk:121: dbus-show-recursive-depends] Error 1
>
> Drop support for bluez_utils. For bluez5_utils, which also depends on
> dbus, we only need the headers in the bluez5_utils-headers package. Use
> that to break the circular dependency.
>
> Fixes:
> http://autobuild.buildroot.net/results/9c3/9c3ee798fa6bb501a20a7892c0b085d2b279b664/
>
> Suggested-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> v2: keep bluez5_utils, and use bluez5_utils-headers (Yann)
> ---
> package/libpcap/libpcap.mk | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-18 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-17 19:09 [Buildroot] [PATCH v2] package/libpcap: fix bluez circular dependency Baruch Siach
2019-03-18 20:56 ` Thomas Petazzoni [this message]
2019-03-27 14:37 ` 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=20190318215604.117a03e0@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.