DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Posadas, Emerson" <emerson.posadas@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] pktgen wr_cksum error
Date: Mon, 11 Jul 2016 18:30:03 +0000	[thread overview]
Message-ID: <CA6C5DA2-698D-4829-8A8E-F5923197CDD6@intel.com> (raw)
In-Reply-To: <DC37A2D0D1A435489038224DF610BC9930D2C8C3@FMSMSX106.amr.corp.intel.com>

the line is using C99 option of ‘for (int i = 0; i < X; i++) need to move the declare of the int i out to the function instead of in the for loop.
I have fixed his already, but will make a special patch to update this problem when i can.

> On Jul 11, 2016, at 9:09 AM, Posadas, Emerson <emerson.posadas@intel.com> wrote:
> 
> Hello
> 
> I'm trying to build pktgen-v3.0.05 with dpdk 16.04 for with RTE_TARGET x86_64-native-linuxapp-gcc. Seemts that the build is failing due to an error on wr_cksum.c. Is something I can try to fix this error and build pktgen successfully? Not sure if others have had this error before.
> 
> # make
> == lib
> == common
>  CC wr_cksum.o
> In file included from /root/pktgen-v3.0.05/lib/common/wr_cksum.c:102:0:
> /root/pktgen-v3.0.05/lib/common/wr_mbuf.h: In function '__pktmbuf_alloc_noreset':
> /root/pktgen-v3.0.05/lib/common/wr_mbuf.h:47:2: error: 'for' loop initial declarations are only allowed in C99 mode
> /root/pktgen-v3.0.05/lib/common/wr_mbuf.h:47:2: note: use option -std=c99 or -std=gnu99 to compile your code
> make[3]: *** [wr_cksum.o] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [common] Error 2
> make: *** [lib] Error 2
> root@pktgen:~
> 
> 
> EP
> 


      reply	other threads:[~2016-07-11 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 16:09 Posadas, Emerson
2016-07-11 18:30 ` Wiles, Keith [this message]

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=CA6C5DA2-698D-4829-8A8E-F5923197CDD6@intel.com \
    --to=keith.wiles@intel.com \
    --cc=dev@dpdk.org \
    --cc=emerson.posadas@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).