From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Patil, Harish" <Harish.Patil@cavium.com>,
"Horton, Remy" <remy.horton@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] app/testpmd: compilation error with bitrate/latency config flags disabled
Date: Wed, 3 May 2017 06:51:40 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747815605@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <D52EC808.13E8D0%Harish.Patil@cavium.com>
Hi Harish,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Patil, Harish
> Sent: Wednesday, May 03, 2017 7:34 AM
> To: Horton, Remy; De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] app/testpmd: compilation error with bitrate/latency
> config flags disabled
>
> Hi,
> Seeing compilation errors with DPDK 17.05-rc3 when I happened to disable
> bitrate/latency configs during our internal testing.
> CONFIG_RTE_LIBRTE_BITRATE=n and
> CONFIG_RTE_LIBRTE_LATENCY_STATS=n.
>
> /home/root1/hpatil/17.05-rc3/dpdk/app/test-pmd/testpmd.c: In function
> ?main?:
> /home/root1/hpatil/17.05-rc3/dpdk/app/test-pmd/testpmd.c:2242:2:
> error:
> ?bitrate_enabled? undeclared (first use in this function)
> bitrate_enabled = 0;
> ^
> /home/root1/hpatil/17.05-rc3/dpdk/app/test-pmd/testpmd.c:2242:2:
> note:
> each undeclared identifier is reported only once for each function it
> appears in
> make[5]: *** [testpmd.o] Error 1
> make[5]: *** Waiting for unfinished jobs....
>
> Does the patch you sent for review: "[PATCH] app/testpmd: disable latency
> stats by default” address this?
> Please check.
No, this is a separate issue. I will send a patch to fix it
(also a v2 for the patch that you mentioned, as it needs that fix too).
Thanks for spotting that.
Pablo
>
> Thanks,
>
> harish
>
>
>
prev parent reply other threads:[~2017-05-03 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 6:34 Patil, Harish
2017-05-03 6:51 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D89747815605@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=Harish.Patil@cavium.com \
--cc=dev@dpdk.org \
--cc=remy.horton@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).