DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: stepan <stepan.sojka@adaptivemobile.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-dev, pcap] pcap: fix build of all-in-one shared library
Date: Mon, 8 Dec 2014 09:49:10 -0500	[thread overview]
Message-ID: <20141208144910.GE3237@localhost.localdomain> (raw)
In-Reply-To: <kzlhosux2e.fsf@adaptivemobile.com>

On Tue, Oct 07, 2014 at 12:14:04AM +0100, stepan wrote:
> Build of some of the test binaries fails when the following flags are enabled:
> 
> CONFIG_RTE_LIBRTE_PMD_PCAP=y
> CONFIG_RTE_BUILD_SHARED_LIB=y
> CONFIG_RTE_BUILD_COMBINE_LIBS=y
> 
> The binarieas are missing symbols from libpcap. This
> patch adds the missing '-lpcap' linker flag into the respective Makefiles.
> 
> Signed-off-by: stepan <stepan.sojka@adaptivemobile.com>
> 
> ---
> app/cmdline_test/Makefile | 4 ++++
>  app/dump_cfg/Makefile     | 4 ++++
>  app/test-acl/Makefile     | 4 ++++
>  app/test/Makefile         | 4 ++++
>  4 files changed, 16 insertions(+)
> 
> diff --git a/app/cmdline_test/Makefile b/app/cmdline_test/Makefile
> index e9eafd2..ce44fd5 100644
> --- a/app/cmdline_test/Makefile
> +++ b/app/cmdline_test/Makefile
> @@ -47,6 +47,10 @@ SRCS-y += commands.c
>  CFLAGS += -O3
>  CFLAGS += $(WERROR_FLAGS)
>  
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
> +LDFLAGS += -lpcap
> +endif
> +
>  include $(RTE_SDK)/mk/rte.app.mk
>  
>  endif
> diff --git a/app/dump_cfg/Makefile b/app/dump_cfg/Makefile
> index 3257127..513ce59 100644
> --- a/app/dump_cfg/Makefile
> +++ b/app/dump_cfg/Makefile
> @@ -35,6 +35,10 @@ APP = dump_cfg
>  
>  CFLAGS += $(WERROR_FLAGS)
>  
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
> +LDFLAGS += -lpcap
> +endif
> +
>  # all source are stored in SRCS-y
>  
>  SRCS-y := main.c
> diff --git a/app/test-acl/Makefile b/app/test-acl/Makefile
> index 43dfdcb..ea063fd 100644
> --- a/app/test-acl/Makefile
> +++ b/app/test-acl/Makefile
> @@ -37,6 +37,10 @@ APP = testacl
>  
>  CFLAGS += $(WERROR_FLAGS)
>  
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
> +LDFLAGS += -lpcap
> +endif
> +
>  # all source are stored in SRCS-y
>  SRCS-y := main.c
>  
> diff --git a/app/test/Makefile b/app/test/Makefile
> index 6af6d76..e456140 100644
> --- a/app/test/Makefile
> +++ b/app/test/Makefile
> @@ -145,6 +145,10 @@ CFLAGS_test_kni.o += -Wno-deprecated-declarations
>  endif
>  CFLAGS += -D_GNU_SOURCE
>  
> +ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),y)
> +LDFLAGS += -lpcap
> +endif
> +
>  # this application needs libraries first
>  DEPDIRS-y += lib
>  
Acked-by: Neil Horman <nhorman@tuxdriver.com>

  reply	other threads:[~2014-12-08 14:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 23:14 [dpdk-dev] [pcap PATCH] " stepan
2014-12-08 14:49 ` Neil Horman [this message]
2014-12-15 22:42   ` [dpdk-dev] [dpdk-dev, pcap] " Thomas Monjalon
2014-12-15 23:04     ` [dpdk-dev] [PATCH v2] mk: fix build with shared pcap pmd Thomas Monjalon
2014-12-16 13:58       ` Neil Horman
2014-12-16 14:39         ` Thomas Monjalon
2014-12-16 21:42           ` Neil Horman
2014-12-16 23:37             ` Thomas Monjalon

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=20141208144910.GE3237@localhost.localdomain \
    --to=nhorman@tuxdriver.com \
    --cc=dev@dpdk.org \
    --cc=stepan.sojka@adaptivemobile.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 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).