All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 351] When RTE_LIBRTE_PCAP_PMD is enabled RTE_PORT_PCAP is not enabled for rte_port_source_sink.c
Date: Tue, 24 Sep 2019 08:17:57 +0000	[thread overview]
Message-ID: <bug-351-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=351

            Bug ID: 351
           Summary: When RTE_LIBRTE_PCAP_PMD is enabled RTE_PORT_PCAP is
                    not enabled for rte_port_source_sink.c
           Product: DPDK
           Version: 19.05
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: cristian.bidea@keysight.com
  Target Milestone: ---

Created attachment 68
  --> https://bugs.dpdk.org/attachment.cgi?id=68&action=edit
Patch for missing -lpcap link and RTE_PORT_PCAP option

On the old build system when enabling RTE_LIBRTE_PCAP_PMD an option is enabled
for rte_port_source_sink (RTE_PORT_PCAP) and pcap is linked to librte_port.

On Meson build this doesn't happen. Please see attached patch for a possible
fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-09-24  8:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24  8:17 bugzilla [this message]
2019-09-24 12:04 ` [dpdk-dev] [PATCH] port: fix missing pcap support with meson Bruce Richardson
2019-09-24 15:19   ` Bruce Richardson
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=bug-351-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 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.