All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Jared Bents <jared.bents@rockwellcollins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2, 1/1] package/libvirt: fix libvirtd dependency
Date: Sun, 14 Aug 2022 12:02:20 +0200	[thread overview]
Message-ID: <20220814120220.03c5b28b@windsurf> (raw)
In-Reply-To: <20220814083949.2781340-1-fontaine.fabrice@gmail.com>

Hello Fabrice,

On Sun, 14 Aug 2022 10:39:49 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> Add a dependency to BR2_TOOLCHAIN_USES_GLIBC to fix the following
> libvirtd build failure raised since commit
> f81242ae4fb64ab85af5d38e70246222276552ae:
> 
> Makefile:575: *** libbsd is in the dependency chain of netcat-openbsd that has added it to its _DEPENDENCIES variable without selecting it or depending on it from Config.in.  Stop.
> 
> BR2_TOOLCHAIN_USES_GLIBC is only needed by netcat-openbsd, but a
> dependency on BR2_TOOLCHAIN_USES_GLIBC || !BR2_PACKAGE_NETCAT_OPENBSD
> can't be added as it will create a circular dependency
> 
> An other option would be to revert
> f81242ae4fb64ab85af5d38e70246222276552ae and to always mandate C++ even
> if it is only needed by nmap-ncat

My opinion is that it would make more sense to always mandate C++.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-08-14 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14  8:39 [Buildroot] [PATCH v2, 1/1] package/libvirt: fix libvirtd dependency Fabrice Fontaine
2022-08-14 10:02 ` Thomas Petazzoni via buildroot [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=20220814120220.03c5b28b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=jared.bents@rockwellcollins.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.