From: Kai Ji <kai.ji@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, Kai Ji <kai.ji@intel.com>
Subject: [dpdk-dev v2] Crypto/qat: fix build with OpenSSL 1.1
Date: Tue, 26 Jul 2022 19:56:08 +0800 [thread overview]
Message-ID: <20220726115608.84140-1-kai.ji@intel.com> (raw)
In-Reply-To: <20220726100550.71793-1-kai.ji@intel.com>
This patch add in libcrypto version check before enable libipsec-mb for
QAT. The inter-ipsec-mb lib for partial hash and AES calculation should
only be enabled when both OpensSSL 3.0 and IPSec_MB 1.2.0 are installed
on the system.
Signed-off-by: Kai Ji <kai.ji@intel.com>
---
drivers/common/qat/meson.build | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/common/qat/meson.build b/drivers/common/qat/meson.build
index 245c0fbe61..8247bdd017 100644
--- a/drivers/common/qat/meson.build
+++ b/drivers/common/qat/meson.build
@@ -37,7 +37,9 @@ endif
IMB_required_ver = '1.2.0'
libipsecmb = cc.find_library('IPSec_MB', required: false)
-if libipsecmb.found()
+libcrypto_3 = dependency('libcrypto', required: false,
+ method: 'pkg-config', version : '>=3.0.0')
+if libipsecmb.found() and libcrypto_3.found()
# version comes with quotes, so we split based on " and take the middle
imb_ver = cc.get_define('IMB_VERSION_STR',
prefix : '#include<intel-ipsec-mb.h>').split('"')[1]
--
2.17.1
next prev parent reply other threads:[~2022-07-26 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 9:59 [dpdk-dev v1] crypto/qat: add in libcrypto version check Kai Ji
2022-07-26 10:05 ` [dpdk-dev v2] " Kai Ji
2022-07-26 11:56 ` Kai Ji [this message]
2022-08-04 13:09 ` [EXT] [dpdk-dev v2] Crypto/qat: fix build with OpenSSL 1.1 Akhil Goyal
2022-07-26 10:14 ` [EXT] [dpdk-dev v1] crypto/qat: add in libcrypto version check Akhil Goyal
2022-07-26 11:57 ` Ji, Kai
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=20220726115608.84140-1-kai.ji@intel.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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).