From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 610] Example App like skeleton, l2fwd etc. in DPDK 20.11 need static compilation else will fail during runtime
Date: Sat, 09 Jan 2021 04:33:09 +0000 [thread overview]
Message-ID: <bug-610-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=610
Bug ID: 610
Summary: Example App like skeleton, l2fwd etc. in DPDK 20.11
need static compilation else will fail during runtime
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: yockgen@gmail.com
Target Milestone: ---
Example App like skeleton, l2fwd etc. in DPDK 20.11 (not happened in 20.08)
need static compilation else will fail during runtime with confusing message
like below might led to wrong direction troubleshooting:
===============================================================================
oot@yockgen-VirtualBox://home/yockgen/dpdk/examples/l2fwd# ./build/l2fwd -- -p
0x3
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: No legacy callbacks, legacy socket not created
MAC updating enabled
EAL: Error - exiting with code: 1
Cause: No Ethernet ports - bye
================================================================================
Two options to remedy the problem:
1. make static
2. Added runtime parameter -d (e.g. -d librte_net_e1000.so)
Expected precise error handling message display, as the sample apps mostly the
first entry point for inexperience new users, precise message will really help
reduce the already high learning curve for DPDK.
Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-01-09 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-610-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 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).