From: Jarkko Sakkinen <jarkko@kernel.org>
To: Kristen Carlson Accardi <kristen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Shuah Khan <shuah@kernel.org>,
linux-sgx@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests/sgx: Ignore OpenSSL 3.0 deprecated functions warning
Date: Thu, 28 Jul 2022 11:00:02 +0300 [thread overview]
Message-ID: <YuJCAhfQklzVQJGh@kernel.org> (raw)
In-Reply-To: <20220721194041.43970-1-kristen@linux.intel.com>
On Thu, Jul 21, 2022 at 12:40:40PM -0700, Kristen Carlson Accardi wrote:
> OpenSSL 3.0 deprecates some of the functions used in the SGX
> selftests, causing build errors on new distros. For now ignore
> the warnings until support for the functions is no longer
> available.
>
> Signed-off-by: Kristen Carlson Accardi <kristen@linux.intel.com>
> ---
> tools/testing/selftests/sgx/sigstruct.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tools/testing/selftests/sgx/sigstruct.c b/tools/testing/selftests/sgx/sigstruct.c
> index 50c5ab1aa6fa..bb191b70141a 100644
> --- a/tools/testing/selftests/sgx/sigstruct.c
> +++ b/tools/testing/selftests/sgx/sigstruct.c
> @@ -17,6 +17,9 @@
> #include "defines.h"
> #include "main.h"
>
> +/* OpenSSL 3.0 has deprecated some functions. For now just ignore the warnings. */
Perhaps, even prefix with "FIXME:" prefix?
> +#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
> +
> struct q1q2_ctx {
> BN_CTX *bn_ctx;
> BIGNUM *m;
> --
> 2.36.1
>
BR, Jarkko
prev parent reply other threads:[~2022-07-28 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 19:40 [PATCH] selftests/sgx: Ignore OpenSSL 3.0 deprecated functions warning Kristen Carlson Accardi
2022-07-21 20:02 ` Dave Hansen
2022-07-21 20:08 ` Kristen Carlson Accardi
2022-07-21 20:14 ` Dave Hansen
2022-07-28 8:00 ` Jarkko Sakkinen [this message]
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=YuJCAhfQklzVQJGh@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=shuah@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.