From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/netsniff-ng: Allow to build with uclibc but w/o mausezahn
Date: Thu, 28 Mar 2019 18:56:12 +0100 [thread overview]
Message-ID: <20190328185612.493d0b70@windsurf> (raw)
In-Reply-To: <20190304085741.13782-1-vadim4j@gmail.com>
Hello Vadim,
On Mon, 4 Mar 2019 10:57:41 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> mausezahn can't be build with uclibc because uclibc
> does not provide ceill() function, so it does not allow
> to build all netsniff-ng's tools with uclibc.
>
> Fix it by moving mausezahn under separate config option,
> which has own dependencies and packages selection (libnet & libcli).
>
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
Applied to master with a few changes.
> -config BR2_PACKAGE_NETSNIFF_NG
> +menuconfig BR2_PACKAGE_NETSNIFF_NG
Kept "config" here. We don't typically have a "menuconfig" for just one
sub-option.
> +NETSNIFF_NG_TOOLS = netsniff-ng trafgen astraceroute flowtop ifpps bpfc curvetun
I changed this to use the allbutmausezahn and install_allbutmausezahn targets.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-03-28 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 8:57 [Buildroot] [PATCH 1/1] package/netsniff-ng: Allow to build with uclibc but w/o mausezahn Vadim Kochan
2019-03-04 19:06 ` Arnout Vandecappelle
2019-03-06 5:29 ` Vadim Kochan
2019-03-06 9:28 ` Arnout Vandecappelle
2019-03-28 17:16 ` Thomas Petazzoni
2019-03-28 17:15 ` Thomas Petazzoni
2019-03-28 17:41 ` Vadym Kochan
2019-03-28 17:56 ` Thomas Petazzoni [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=20190328185612.493d0b70@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox