From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/aesni_mb: fix compile
Date: Mon, 21 Jan 2019 22:42:54 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258010D90668C@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20190121155611.74873-1-roy.fan.zhang@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fan Zhang
> Sent: Monday, January 21, 2019 3:56 PM
> To: dev@dpdk.org
> Cc: akhil.goyal@nxp.com
> Subject: [dpdk-dev] [PATCH v2] crypto/aesni_mb: fix compile
>
> This patch fixes the inflexible compile issue AESNI-MB PMD.
> Originally the compile of the PMD will fail if IPSec_MB is
> not installed in default location.
>
> Fixes: c68d7aa354f6 ("crypto/aesni_mb: use architecture independent macros")
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> v2:
> - uses standard head invocation
>
> drivers/crypto/aesni_mb/Makefile | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/aesni_mb/Makefile b/drivers/crypto/aesni_mb/Makefile
> index 7ef290dc5..8d2024c9e 100644
> --- a/drivers/crypto/aesni_mb/Makefile
> +++ b/drivers/crypto/aesni_mb/Makefile
> @@ -23,7 +23,9 @@ LDLIBS += -lrte_eal -lrte_mbuf -lrte_mempool -lrte_ring
> LDLIBS += -lrte_cryptodev
> LDLIBS += -lrte_bus_vdev
>
> -IMB_HDR = /usr/include/intel-ipsec-mb.h
> +IMB_HDR = $(shell echo '\#include <intel-ipsec-mb.h>' | \
> + $(CC) -E $(EXTRA_CFLAGS) - | grep 'intel-ipsec-mb.h' | \
> + head -n1 | cut -d'"' -f2)
>
> # Detect library version
> IMB_VERSION = $(shell grep -e "IMB_VERSION_STR" $(IMB_HDR) | cut -d'"' -f2)
> --
Tested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.13.6
next prev parent reply other threads:[~2019-01-21 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 13:21 [dpdk-dev] [PATCH] " Fan Zhang
2019-01-16 16:48 ` De Lara Guarch, Pablo
2019-01-17 22:26 ` Thomas Monjalon
2019-01-18 10:57 ` Ananyev, Konstantin
2019-01-18 11:03 ` Thomas Monjalon
2019-01-18 11:55 ` Ananyev, Konstantin
2019-01-21 10:08 ` Zhang, Roy Fan
2019-01-21 15:56 ` [dpdk-dev] [PATCH v2] " Fan Zhang
2019-01-21 22:42 ` Ananyev, Konstantin [this message]
2019-01-22 16:29 ` 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=2601191342CEEE43887BDE71AB977258010D90668C@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).