From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Verma, Shally" <Shally.Verma@cavium.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
"Sahu, Sunila" <Sunila.Sahu@cavium.com>,
"Kotamarthy, Kanaka" <Kanaka.Kotamarthy@cavium.com>
Subject: Re: [dpdk-dev] dpdk-next-crypto broken?
Date: Tue, 8 May 2018 16:06:58 +0530 [thread overview]
Message-ID: <20180508103657.GA3982@jerin> (raw)
In-Reply-To: <CY4PR0701MB363467B41A2B5EC66D95661CF09A0@CY4PR0701MB3634.namprd07.prod.outlook.com>
-----Original Message-----
> Date: Tue, 8 May 2018 10:31:56 +0000
> From: "Verma, Shally" <Shally.Verma@cavium.com>
> To: "dev@dpdk.org" <dev@dpdk.org>, Pablo de Lara
> <pablo.de.lara.guarch@intel.com>
> CC: "Sahu, Sunila" <Sunila.Sahu@cavium.com>, "Kotamarthy, Kanaka"
> <Kanaka.Kotamarthy@cavium.com>
> Subject: [dpdk-dev] dpdk-next-crypto broken?
>
> Trying to do 'make test' on dpdk-next-crypto clone, throw these error. Even if I try to disable this file build by setting CONFIG_RTE_LIBRTE_EVENTDEV=n , don't help, fails at some other places. Can there be quick resolve for same?
Are you using gcc 4.8.5. If so the following patch will fix the problem.
http://dpdk.org/dev/patchwork/patch/39428/
>
> CC test_event_timer_adapter.o
> /home/sverma/dpdk/latest/test/test/test_event_timer_adapter.c: In function 'test_timer_state':
> /home/sverma/dpdk/latest/test/test/test_event_timer_adapter.c:381:3: error: missing initializer for field 'priority' of 'struct <anonymous>' [-Werror=missing-field-initializers]
> .ev.sched_type = RTE_SCHED_TYPE_ATOMIC,
> ^
> In file included from /home/sverma/dpdk/latest/test/test/test_event_timer_adapter.c:12:0:
> /home/sverma/dpdk/latest/build/include/rte_eventdev.h:1049:12: note: 'priority' declared here
> uint8_t priority;
> ^
>
> Thanks
> Shally
next prev parent reply other threads:[~2018-05-08 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 10:31 Verma, Shally
2018-05-08 10:36 ` Jerin Jacob [this message]
2018-05-08 10:47 ` Verma, Shally
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=20180508103657.GA3982@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=Kanaka.Kotamarthy@cavium.com \
--cc=Shally.Verma@cavium.com \
--cc=Sunila.Sahu@cavium.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).