From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "asomalap@amd.com" <asomalap@amd.com>,
"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] OpenSSL 3.0 released, deprecated functions - DPDK crypto compilation issues
Date: Wed, 15 Sep 2021 12:01:43 +0000 [thread overview]
Message-ID: <PH0PR11MB501308B9F89F16A3469089309FDB9@PH0PR11MB5013.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR18MB4484532A94B29183C088EDFAD8DB9@CO6PR18MB4484.namprd18.prod.outlook.com>
Sure Akhil, will do some more testing and will send (unless some better proposal come in). It needs to be backported as well.
From: Akhil Goyal <gakhil@marvell.com>
Sent: Wednesday, September 15, 2021 12:51 PM
To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; dev@dpdk.org
Cc: asomalap@amd.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>; Doherty, Declan <declan.doherty@intel.com>
Subject: RE: OpenSSL 3.0 released, deprecated functions - DPDK crypto compilation issues
Hi Arek,
Can you submit changes for the meson files needed to compile it with 3.0 if needed?
Regards,
Akhil
From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com<mailto:arkadiuszx.kusztal@intel.com>>
Sent: Wednesday, September 15, 2021 4:02 PM
To: dev@dpdk.org<mailto:dev@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com<mailto:gakhil@marvell.com>>; asomalap@amd.com<mailto:asomalap@amd.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com<mailto:roy.fan.zhang@intel.com>>; Doherty, Declan <declan.doherty@intel.com<mailto:declan.doherty@intel.com>>
Subject: [EXT] OpenSSL 3.0 released, deprecated functions - DPDK crypto compilation issues
External Email
________________________________
Hi,
OpenSSL 3.0 is now released and since some PMDs in DPDK depends on libcrypto deprecated now functions, anyone who install 3.0 may see compilation problems.
So we suggest in case adaptation cannot be made in time to put version constraint in meson dependencies "version : '<3.0.0'", it probably will not work with OpenSSL installed from source though (at least did not work for me).
Regards,
Arek
next prev parent reply other threads:[~2021-09-15 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 10:31 Kusztal, ArkadiuszX
2021-09-15 10:50 ` Akhil Goyal
2021-09-15 12:01 ` Kusztal, ArkadiuszX [this message]
2021-10-08 13:10 ` Zhang, Roy Fan
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=PH0PR11MB501308B9F89F16A3469089309FDB9@PH0PR11MB5013.namprd11.prod.outlook.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=asomalap@amd.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--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).