DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] dpaa2: building with EXTRA_CFLAGS="-g -O0" and shared libs link error
Date: Mon, 20 Aug 2018 12:08:34 +0000	[thread overview]
Message-ID: <9D2E64E2-8DA8-454B-B3FF-117703C793BE@intel.com> (raw)
In-Reply-To: <VI1PR0401MB25410FA2475DCC114303779489320@VI1PR0401MB2541.eurprd04.prod.outlook.com>



> On Aug 20, 2018, at 2:33 AM, Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> 
> Hi Keith,
> 	I am able to reproduce the issue. We will send the fix asap.

Thanks Hemant.
> 
> Regards,
> Hemant
> 
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Wiles, Keith
> Sent: Sunday, August 19, 2018 8:25 PM
> To: DPDK <dev@dpdk.org>
> Subject: [dpdk-dev] dpaa2: building with EXTRA_CFLAGS="-g -O0" and shared libs link error
> 
> 
> I am building on Ubuntu 18.04.1 LTS, gcc 7.3.0-16ubuntu3 and with EXTRA_CFLAGS=“-g -O0” with shared libs enabled.
> 
> I get an undefined reference to rte_dpaa2_memsegs when building portal/dpaa2_hw_dpio.c in the link phase.
> 
> The odd part is this does not happen unless you are building with EXTRA_CFLAGS and with shared libs enabled.
> 
> It seems to have circular dependency on drivers/mempool/dpaa2 and drivers/bus/fslmc/portal
> 
> This breaks being able to build a debug version of DPDK.
> 
> 
> Regards,
> Keith
> 

Regards,
Keith


      reply	other threads:[~2018-08-20 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-19 14:55 Wiles, Keith
2018-08-20  7:33 ` Hemant Agrawal
2018-08-20 12:08   ` Wiles, Keith [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=9D2E64E2-8DA8-454B-B3FF-117703C793BE@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.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).