From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 67] multi_process/l2fwd_fork failed to compile
Date: Mon, 02 Jul 2018 02:13:23 +0000 [thread overview]
Message-ID: <bug-67-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=67
Bug ID: 67
Summary: multi_process/l2fwd_fork failed to compile
Product: DPDK
Version: 18.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: wanglifu@infoch.cn
Target Milestone: ---
CC main.o
/root/dpdk-18.05/examples/multi_process/l2fwd_fork/main.c: In function ‘main’:
/root/dpdk-18.05/examples/multi_process/l2fwd_fork/main.c:1043:33: error:
‘dev_info’ undeclared (first use in this function)
rte_eth_dev_info_get(portid, &dev_info);
^
/root/dpdk-18.05/examples/multi_process/l2fwd_fork/main.c:1043:33: note: each
undeclared identifier is reported only once for each function it appears in
/root/dpdk-18.05/examples/multi_process/l2fwd_fork/main.c:1077:11: error:
‘struct rte_eth_txconf’ has no member named ‘tx_offloads’
txq_conf.tx_offloads = local_port_conf.txmode.offloads;
^
make[1]: *** [main.o] Error 1
make: *** [all] Error 2
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-07-02 2:13 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-67-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).