DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Qiming Yang <qiming.yang@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] net/ice: fix build with debug enabled
Date: Thu, 3 Jan 2019 12:41:32 +0000	[thread overview]
Message-ID: <e077db7d-1381-3a64-cede-8745ce13d540@intel.com> (raw)
In-Reply-To: <20181227060553.11195-1-jerinj@marvell.com>

On 12/27/2018 6:06 AM, Jerin Jacob Kollanukkaran wrote:
> When RTE_LIBRTE_MBUF_DEBUG enabled, rte_mbuf_sanity_check()
> function defined in rte_mbuf.so library,
> add it while linking the librte_pmd_ice.so library to fix
> the build issue.
> 
> error log:
> /usr/bin/ld: ice_rxtx.o: in function `ice_recv_pkts':
> ice_rxtx.c:(.text+0x1d97): undefined reference to
> `rte_mbuf_sanity_check'
> /usr/bin/ld: ice_rxtx.o: in function
> `ice_tx_queue_release_mbufs':
> ice_rxtx.c:(.text+0x21e0): undefined reference to
> `rte_mbuf_sanity_check'
> /usr/bin/ld: ice_rxtx.c:(.text+0x22b3): undefined reference
> to `rte_mbuf_sanity_check'
> /usr/bin/ld: ice_rxtx.c:(.text+0x24a0): undefined reference
> to `rte_mbuf_sanity_check'
> /usr/bin/ld: ice_rxtx.c:(.text+0x2640): undefined reference
> to `rte_mbuf_sanity_check'
> /usr/bin/ld: ice_rxtx.o:ice_rxtx.c:(.text+0x299f):
> more undefined references to `rte_mbuf_sanity_check' follow
> 
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>

    Fixes: 50370662b727 ("net/ice: support device and queue ops")

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2019-01-03 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  6:06 Jerin Jacob Kollanukkaran
2019-01-03 12:41 ` Ferruh Yigit [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=e077db7d-1381-3a64-cede-8745ce13d540@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=qiming.yang@intel.com \
    --cc=thomas@monjalon.net \
    --cc=wenzhuo.lu@intel.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).