All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libpcap: disable bluez to avoid circular dependency
Date: Sun, 17 Mar 2019 20:47:35 +0200	[thread overview]
Message-ID: <878sxdz6bc.fsf@tarshish> (raw)
In-Reply-To: <20190317183155.GG14237@scaer>

Hi Yann,

On Sun, Mar 17 2019, Yann E. MORIN wrote:
> On 2019-03-17 18:54 +0200, Baruch Siach spake thusly:
>> 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
>>
>> Like in the case of dbus (commit b01d463c140) the bluez_utils dependency
>> looks less useful.
>
> Sorry, but in this case I disagree: being able to actually dissect
> bluetooth packets *is* very interesting.

Debian for one does not make libpcap depend on bluez. I don't know about
others.

>> Disable bluetooth support unconditionally.
>
> Sorry again, but the loop is only about bluez_utils, not bluez5_utils.
> So, why can't we at the very least keep the depenency on bluez5_utils?

bluez5_utils depend on dbus as well.

> And if there still is a loop with that, then we do have bluez5_utils-headers
> than may help.

I'll take a look.

Thanks,
baruch

>> Fixes:
>> http://autobuild.buildroot.net/results/9c3/9c3ee798fa6bb501a20a7892c0b085d2b279b664/
>>
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>> ---
>>  package/libpcap/libpcap.mk | 12 ++----------
>>  1 file changed, 2 insertions(+), 10 deletions(-)
>>
>> diff --git a/package/libpcap/libpcap.mk b/package/libpcap/libpcap.mk
>> index 83188c8c4847..82461390de4d 100644
>> --- a/package/libpcap/libpcap.mk
>> +++ b/package/libpcap/libpcap.mk
>> @@ -16,8 +16,8 @@ LIBPCAP_CONF_ENV = \
>>  	CFLAGS="$(LIBPCAP_CFLAGS)"
>>  LIBPCAP_CFLAGS = $(TARGET_CFLAGS)
>>  LIBPCAP_CONF_OPTS = --disable-yydebug --with-pcap=linux --without-dag
>> -# Disable dbus to break recursive dependencies
>> -LIBPCAP_CONF_OPTS += --disable-dbus
>> +# Disable dbus and bluez_utils to break recursive dependencies
>> +LIBPCAP_CONF_OPTS += --disable-dbus --disable-bluetooth
>>  LIBPCAP_CONFIG_SCRIPTS = pcap-config
>>
>>  # Omit -rpath from pcap-config output
>> @@ -26,14 +26,6 @@ define LIBPCAP_CONFIG_REMOVE_RPATH
>>  endef
>>  LIBPCAP_POST_BUILD_HOOKS = LIBPCAP_CONFIG_REMOVE_RPATH
>>
>> -ifeq ($(BR2_PACKAGE_BLUEZ_UTILS),y)
>> -LIBPCAP_DEPENDENCIES += bluez_utils
>> -else ifeq ($(BR2_PACKAGE_BLUEZ5_UTILS),y)
>> -LIBPCAP_DEPENDENCIES += bluez5_utils
>> -else
>> -LIBPCAP_CONF_OPTS += --disable-bluetooth
>> -endif
>> -
>>  ifeq ($(BR2_PACKAGE_LIBNL),y)
>>  LIBPCAP_DEPENDENCIES += libnl
>>  LIBPCAP_CFLAGS += "-I$(STAGING_DIR)/usr/include/libnl3"

--
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -

      reply	other threads:[~2019-03-17 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-17 16:54 [Buildroot] [PATCH] package/libpcap: disable bluez to avoid circular dependency Baruch Siach
2019-03-17 18:31 ` Yann E. MORIN
2019-03-17 18:47   ` Baruch Siach [this message]

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=878sxdz6bc.fsf@tarshish \
    --to=baruch@tkos.co.il \
    --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.