From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [DPDK] broken compilation when RTE_LIBRTE_SECURITY is not enabled
Date: Mon, 14 Oct 2019 10:14:04 +0200 [thread overview]
Message-ID: <1b29edf2-367d-1a2d-ffce-7fd079ba669b@6wind.com> (raw)
Hello,
When disabling RTE_LIBRTE_SECURITY, DPDK compilation fails with the
following error messages:
CC test_cryptodev.o
/home/herbelot/work/dpdk/app/test/test_cryptodev.c:76:40: error: field
‘type’ has incomplete type
enum rte_security_session_action_type type;
^~~~
/home/herbelot/work/dpdk/app/test/test_cryptodev.c: In function
‘ut_teardown’:
/home/herbelot/work/dpdk/app/test/test_cryptodev.c:576:25: error:
‘RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL’ undeclared (first use in
this function)
if (ut_params->type == RTE_SECURITY_ACTION_TYPE_LOOKASIDE_PROTOCOL) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/herbelot/work/dpdk/app/test/test_cryptodev.c:576:25: note: each
undeclared identifier is reported only once for each function it appears in
/home/herbelot/work/dpdk/app/test/test_cryptodev.c:578:4: error:
implicit declaration of function ‘rte_security_session_destroy’; did you
mean ‘rte_cryptodev_pmd_destroy’? [-Werror=implicit-function-declaration]
rte_security_session_destroy(rte_cryptodev_get_sec_ctx
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
rte_cryptodev_pmd_destroy
/home/herbelot/work/dpdk/app/test/test_cryptodev.c:578:4: error: nested
extern declaration of ‘rte_security_session_destroy’
[-Werror=nested-externs]
Indeed, in commit d883e6e7131b ('test/crypto: add PDCP C-Plane encap
cases'), RTE_SECURITY features are used outside of an "ifdef".
Thanks
Thierry
--
Thierry Herbelot
6WIND
Senior Software Engineer
reply other threads:[~2019-10-14 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1b29edf2-367d-1a2d-ffce-7fd079ba669b@6wind.com \
--to=thierry.herbelot@6wind.com \
--cc=dev@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).