DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gao, DaxueX" <daxuex.gao@intel.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: Chandubabu Namburu <chandu@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 1/1] drivers: define OPENSSL_API_COMPAT
Date: Fri, 13 May 2022 10:02:47 +0000	[thread overview]
Message-ID: <MW4PR11MB5799E8683157A90CFE6644D19DCA9@MW4PR11MB5799.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220510150635.61975-1-heinrich.schuchardt@canonical.com>



> -----Original Message-----
> From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> Sent: 2022年5月10日 23:07
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Cc: Chandubabu Namburu <chandu@amd.com>; dev@dpdk.org; Heinrich
> Schuchardt <heinrich.schuchardt@canonical.com>
> Subject: [PATCH 1/1] drivers: define OPENSSL_API_COMPAT
> 
> The API of the OpenSSL library has changed with version 3.0. This results in a lot
> of compiler warnings like
> 
>     ../dpdk/drivers/crypto/ccp/ccp_crypto.c:182:9:
>     warning: ‘SHA256_Transform’ is deprecated:
>     Since OpenSSL 3.0 [-Wdeprecated-declarations]
> 
> As many Linux distributions still use elder OpenSSL libraries we cannot change
> the used API now. Instead define OPENSSL_API_COMPAT to indicate that we are
> using the OpenSSL 1.1.0 API.
> 
> OPENSSL_API_COMPAT is introduced in *.c files and not in *.h files as some *.c
> files directly include OpenSSL headers.
> 
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
Tested-by: Daxue Gao <daxuex.gao@intel.com>

  reply	other threads:[~2022-05-13 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 15:06 Heinrich Schuchardt
2022-05-13 10:02 ` Gao, DaxueX [this message]
2022-05-17 12:03 ` David Marchand
2022-05-26 16:18   ` [EXT] " Akhil Goyal
2022-05-17 16:30 ` 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=MW4PR11MB5799E8683157A90CFE6644D19DCA9@MW4PR11MB5799.namprd11.prod.outlook.com \
    --to=daxuex.gao@intel.com \
    --cc=chandu@amd.com \
    --cc=dev@dpdk.org \
    --cc=heinrich.schuchardt@canonical.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).