From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, Cristian Bidea <cristian.bidea@keysight.com>
Subject: Re: [dpdk-dev] [PATCH] port: fix missing pcap support with meson
Date: Tue, 24 Sep 2019 16:19:55 +0100 [thread overview]
Message-ID: <20190924151955.GA880@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20190924120414.67793-1-bruce.richardson@intel.com>
On Tue, Sep 24, 2019 at 01:04:14PM +0100, Bruce Richardson wrote:
> The meson build was missing the define to enable pcap port support if
> libpcap (development) package was found on the build platform. Rather than
> duplicating the checks for libpcap found in the pcap net PMD build file, we
> can move the checks to the top-level config directory and reference the
> RTE_PCAP_PORT setting elsewhere in the build.
>
> Bugzilla ID: 351
> Fixes: 5b9656b157d3 ("lib: build with meson")
>
> Cc: stable@dpdk.org
> Reported-by: Cristian Bidea <cristian.bidea@keysight.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Based on response given in bugzilla
[https://bugs.dpdk.org/show_bug.cgi?id=351]
Tested-by: Cristian Bidea <cristian.bidea@keysight.com>
Just adding here so it shows up in patchwork.
/Bruce
next prev parent reply other threads:[~2019-09-24 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 8:17 [dpdk-dev] [Bug 351] When RTE_LIBRTE_PCAP_PMD is enabled RTE_PORT_PCAP is not enabled for rte_port_source_sink.c bugzilla
2019-09-24 12:04 ` [dpdk-dev] [PATCH] port: fix missing pcap support with meson Bruce Richardson
2019-09-24 15:19 ` Bruce Richardson [this message]
2019-10-27 11:57 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-09-24 14:35 ` [dpdk-dev] [Bug 351] When RTE_LIBRTE_PCAP_PMD is enabled RTE_PORT_PCAP is not enabled for rte_port_source_sink.c bugzilla
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=20190924151955.GA880@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=cristian.bidea@keysight.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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;
as well as URLs for NNTP newsgroup(s).