From: "Patil, Harish" <Harish.Patil@cavium.com>
To: "liang.j.ma@intel.com" <liang.j.ma@intel.com>,
"peter.mccarthy@intel.com" <peter.mccarthy@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Compilation errors in drivers/event/opdl/
Date: Sat, 20 Jan 2018 05:18:30 +0000 [thread overview]
Message-ID: <D6881123.1A3A3D%Harish.Patil@cavium.com> (raw)
Hi,
I am seeing below compilation errors in drivers/event/opdl/, this is with
cloned latest DPDK (git clone http://dpdk.org/git/dpdk).
..
..
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c: In function âopdl_xstats_get_namesâ:
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c:89:2: error: âforâ loop initial declarations are only allowed in
C99 mode
for (uint32_t j = 0; j < max_num_port_xstat; j++) {
^
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c:89:2: note: use option -std=c99 or -std=gnu99 to compile your code
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c: In function âopdl_xstats_getâ:
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c:124:2: error: âforâ loop initial declarations are only allowed in
C99 mode
for (uint32_t i = 0; i < n; i++) {
^
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c: In function âopdl_xstats_get_by_nameâ:
/home2/hpatil/e4/jan19-inbox-submit/dpdk/drivers/event/opdl/opdl_evdev_xsta
ts.c:145:2: error: âforâ loop initial declarations are only allowed in
C99 mode
for (uint32_t i = 0; i < max_index; i++) {
..
..
^
Thanks,
Harish
next reply other threads:[~2018-01-20 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 5:18 Patil, Harish [this message]
2018-01-20 8:44 ` Thomas Monjalon
2018-01-21 17:34 ` Stephen Hemminger
2018-01-21 17:49 ` Thomas Monjalon
2018-01-26 17:39 ` Adrien Mazarguil
2018-01-20 8:56 ` Jerin Jacob
2018-01-22 18:38 ` Patil, Harish
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=D6881123.1A3A3D%Harish.Patil@cavium.com \
--to=harish.patil@cavium.com \
--cc=dev@dpdk.org \
--cc=liang.j.ma@intel.com \
--cc=peter.mccarthy@intel.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).