From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 567] l2fwd-static built with Makefile fails to run
Date: Wed, 28 Oct 2020 11:41:34 +0000 [thread overview]
Message-ID: <bug-567-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=567
Bug ID: 567
Summary: l2fwd-static built with Makefile fails to run
Product: DPDK
Version: 20.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: getelson@nvidia.com
Target Milestone: ---
Created attachment 130
--> https://bugs.dpdk.org/attachment.cgi?id=130&action=edit
make command log
DPDK version: 20.11-rc1 (4669252e04)
system:
Linux 3.10.0-693.el7.x86_64
Red Hat Enterprise Linux Server release 7.4 (Maipo)
command:
build/l2fwd-static -w 0000:37:00.0 -- -p 1
EAL: Detected 36 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: failed to parse device "0000:37:00.0"
EAL: Unable to parse device '0000:37:00.0'
EAL: Error - exiting with code: 1
Cause: Invalid EAL arguments
reproduction:
meson --werror --buildtype=debug --prefix=$PWD/dpdk-install build && ninja -C
build && ninja-build -C build install
export PKG_CONFIG_PATH=$PWD/dpdk-install/lib64/pkgconfig
cd examples/l2fwd
make static
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-10-28 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 11:41 bugzilla [this message]
2020-10-29 16:27 ` bugzilla
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-567-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).