From: "Jeff Tarkington (jtarking)" <jtarking@cisco.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Compile / Build Issue - CentOS 7
Date: Mon, 25 Apr 2016 18:03:01 +0000 [thread overview]
Message-ID: <D343D414.2BA91%jtarking@cisco.com> (raw)
Trying to build latest version pulled from git as of today and having a problem with seems to be a member of a struct that is missing. Any thoughts?
Please let me know if there is another place that I should post this type of question.
Thanks,
Jeff
CC pktgen-stats.o
/root/pktgen-dpdk/app/pktgen-stats.c: In function 'pktgen_page_stats':
/root/pktgen-dpdk/app/pktgen-stats.c:353:26: error: 'eth_stats_t' has no member named 'imcasts'
pktgen.cumm_rate_totals.imcasts += info->rate_stats.imcasts;
^
/root/pktgen-dpdk/app/pktgen-stats.c:353:54: error: 'eth_stats_t' has no member named 'imcasts'
pktgen.cumm_rate_totals.imcasts += info->rate_stats.imcasts;
^
/root/pktgen-dpdk/app/pktgen-stats.c: In function 'pktgen_process_stats':
/root/pktgen-dpdk/app/pktgen-stats.c:544:8: error: 'struct rte_eth_stats' has no member named 'imcasts'
stats.imcasts += info->init_stats.imcasts;
^
/root/pktgen-dpdk/app/pktgen-stats.c:544:36: error: 'eth_stats_t' has no member named 'imcasts'
stats.imcasts += info->init_stats.imcasts;
^
/root/pktgen-dpdk/app/pktgen-stats.c:573:19: error: 'eth_stats_t' has no member named 'imcasts'
info->rate_stats.imcasts += stats.imcasts -
^
/root/pktgen-dpdk/app/pktgen-stats.c:573:36: error: 'struct rte_eth_stats' has no member named 'imcasts'
info->rate_stats.imcasts += stats.imcasts -
^
/root/pktgen-dpdk/app/pktgen-stats.c:574:27: error: 'eth_stats_t' has no member named 'imcasts'
info->init_stats.imcasts;
^
make[2]: *** [pktgen-stats.o] Error 1
make[1]: *** [all] Error 2
make: *** [app] Error 2
next reply other threads:[~2016-04-25 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 18:03 Jeff Tarkington (jtarking) [this message]
2016-04-25 18:21 Wiles, Keith
2016-04-25 18:40 ` Wiles, Keith
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=D343D414.2BA91%jtarking@cisco.com \
--to=jtarking@cisco.com \
--cc=users@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).