From: Bruce Richardson <bruce.richardson@intel.com>
To: Truring Team <truring12@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK 20.11 Static vs Dynamic Linking- l2fwd issue
Date: Tue, 19 Jan 2021 10:40:10 +0000 [thread overview]
Message-ID: <20210119104010.GC1786@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CALvshjNGAVPZDswk9_K21pzof9RCstYLun7H+g0g64g+Kh4fXw@mail.gmail.com>
On Tue, Jan 19, 2021 at 03:36:18PM +0530, Truring Team wrote:
> Hi Team,
>
> I am facing one issue with dpdk 20.11 Release, compiled the l2fwd app with
> make static , its throwing following error while running the app:
>
> Problematic Use Case:
> cd dpdk-20.11/examples/l2fwd
> export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
> *make static *
> ./build/l2fwd -l 0-3 -n 4 -- -q 1 -p 1
> EAL: Detected 6 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: No available hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: No legacy callbacks, legacy socket not created
> MAC updating enabled
>
> *EAL: Error - exiting with code: 1 Cause: No Ethernet ports - bye*
>
<snip>
> Can someone help me to figure out the root cause why this happening.
>
It seems like the static libs for the drivers are not linked in for the
"make static" case. Can you please check the following:
* What OS/distro are you using, and what is the pkg-config version? The
version of pkg-config included in RHEL/Centos is known to have some
issues in linking DPDK.
* What is the output when you run "pkg-config --static --libs libdpdk"
next prev parent reply other threads:[~2021-01-19 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 10:06 Truring Team
2021-01-19 10:40 ` Bruce Richardson [this message]
2021-01-19 10:42 ` Bruce Richardson
2021-01-19 11:21 ` Truring Team
2021-01-19 11:24 ` Truring Team
2021-01-19 12:44 ` Bruce Richardson
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=20210119104010.GC1786@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=truring12@gmail.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).