From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] test/eventdev: fix compilation with crypto disabled
Date: Thu, 6 Apr 2017 20:39:30 +0530 [thread overview]
Message-ID: <20170406150928.GA21546@jerin> (raw)
In-Reply-To: <20170406141337.14167-1-olivier.matz@6wind.com>
-----Original Message-----
> Date: Thu, 6 Apr 2017 16:13:37 +0200
> From: Olivier Matz <olivier.matz@6wind.com>
> To: dev@dpdk.org
> CC: jerin.jacob@caviumnetworks.com
> Subject: [PATCH] test/eventdev: fix compilation with crypto disabled
> X-Mailer: git-send-email 2.11.0
>
> There is a compilation error in the following case:
>
> make config T=x86_64-native-linuxapp-gcc
> sed -i 's,CONFIG_RTE_LIBRTE_CRYPTODEV=y,CONFIG_RTE_LIBRTE_CRYPTODEV=n,' \
> build/.config
> sed -i 's,CONFIG_RTE_APP_CRYPTO_PERF=y,CONFIG_RTE_APP_CRYPTO_PERF=n,' \
> build/.config
> make -j4
> make -j4 test-build
>
> test_eventdev.c:39:27: fatal error:
> rte_cryptodev.h: No such file or directory
> #include <rte_cryptodev.h>
> ^
>
> Removing the include induces a new error, (missing declaration of
> rte_eal_vdev_init()), which is fixed by including rte_dev.h.
>
> Fixes: f8f9d233ea0e ("test/eventdev: add unit tests")
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> ---
> test/test/test_eventdev.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/test/test/test_eventdev.c b/test/test/test_eventdev.c
> index b568470a2..5bd46346d 100644
> --- a/test/test/test_eventdev.c
> +++ b/test/test/test_eventdev.c
> @@ -36,7 +36,7 @@
> #include <rte_malloc.h>
> #include <rte_memcpy.h>
> #include <rte_eventdev.h>
> -#include <rte_cryptodev.h>
> +#include <rte_dev.h>
>
> #include "test.h"
>
> --
> 2.11.0
>
next prev parent reply other threads:[~2017-04-06 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 14:13 Olivier Matz
2017-04-06 15:09 ` Jerin Jacob [this message]
2017-04-06 15:35 ` Thomas Monjalon
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=20170406150928.GA21546@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).