From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/netsniff: fix missing depend on statements
Date: Sun, 13 Dec 2015 19:05:32 +0100 [thread overview]
Message-ID: <20151213190532.3fc1ab96@free-electrons.com> (raw)
In-Reply-To: <1450023577-5019-1-git-send-email-s.martin49@gmail.com>
Dear Samuel Martin,
On Sun, 13 Dec 2015 17:19:37 +0100, Samuel Martin wrote:
> Add missing architecture dependencies inherited from liburcu.
>
> Fixes:
> http://autobuild.buildroot.org/results/0a9/0a90d7c8f523b90b8a4ca6312ab4835547590fb2/
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> ---
> package/netsniff-ng/Config.in | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/netsniff-ng/Config.in b/package/netsniff-ng/Config.in
> index 8c48f39..65b2a0f 100644
> --- a/package/netsniff-ng/Config.in
> +++ b/package/netsniff-ng/Config.in
> @@ -11,14 +11,17 @@ config BR2_PACKAGE_NETSNIFF_NG
> depends on BR2_TOOLCHAIN_USES_GLIBC
> depends on BR2_TOOLCHAIN_HAS_THREADS
> depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_58854 # liburcu
> + depends on BR2_arm || BR2_armeb || BR2_aarch64 || BR2_i386 || BR2_powerpc || BR2_x86_64 # liburcu
The list of architecture dependencies from liburcu is already
duplicated in liburcu (two times), in lttng-libust (two times),
lttng-tools (two times) and now in netsniff (three times).
Isn't it time to switch to BR2_PACKAGE_LIBURCU_ARCH_SUPPORTS ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-13 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 16:19 [Buildroot] [PATCH] package/netsniff: fix missing depend on statements Samuel Martin
2015-12-13 17:23 ` Yann E. MORIN
2015-12-13 18:05 ` Thomas Petazzoni [this message]
2015-12-13 18:28 ` Samuel Martin
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=20151213190532.3fc1ab96@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.