All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "acc@openeuler.org" <acc@openeuler.org>
Subject: RE: [EXT] Re: crypto/uadk: introduce uadk crypto driver
Date: Wed, 19 Oct 2022 14:25:09 +0000	[thread overview]
Message-ID: <CO6PR18MB448421DD74F7F59E3EEE0349D82B9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CABQgh9HOMSdJQAe-uWovAV8kFbU30V-J_aSdyetg+4FfVfxBLA@mail.gmail.com>

Hi Zhangfei,
> Hi, Akhil
> 
> On Mon, 17 Oct 2022 at 15:02, Akhil Goyal <gakhil@marvell.com> wrote:
> >
> > Hi everyone,
> >
> >
> >
> > We have a new crypto PMD submitted on ML
> (http://patches.dpdk.org/project/dpdk/cover/20221008083747.6559-1-zhangfei.gao@linaro.org/  )
> >
> >
> >
> > This PMD is dependent on an external library which needs to be cross compiled
> for ARM on x86.
> >
> > It mandatorily need “numactl” also cross-compiled and instead of using pkg-
> config of libnuma, it need the library and headers to be copied manually to aarch
> toolchain.
> >
> > And if that is also done, it is not generating pkg-config which DPDK can use to
> compile the PMD.
> 
> Thanks for the guidance.
> 
> The udak library [1] now support x86 local build, and export pkg-config.
> I have verified the crypto pmd on both x86 and arm with pkg-config feature.
> Though x86 only support build and install, but not test since no hardware.
> 
> v4: https://patches.dpdk.org/project/dpdk/cover/20221019125753.1700071-1-zhangfei.gao@linaro.org/
> 
> [1] https://github.com/Linaro/uadk
> 

I am getting below error with openssl 3.0
Do you have a dependency with earlier versions in uadk? If so, can you fix configure.ac in uadk
to check for version and skip crypto if dependency is not met.


gcc -DHAVE_CONFIG_H -I. -I../..  -DUSE_ZLIB  -Wall -Werror -fno-strict-aliasing -I../../include -g -O2 -MT zip_sva_perf-test_lib.o -MD -MP -MF .deps/zip_sva_perf-test_lib.Tpo -c -o zip_sva_perf-test_lib.o `test -f 'test_lib.c' || echo './'`test_lib.c
test_lib.c: In function ‘calculate_md5’:
test_lib.c:762:2: error: ‘MD5_Init’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
  762 |  MD5_Init(&md5->md5_ctx);
      |  ^~~~~~~~
In file included from test_lib.h:11,
                 from test_lib.c:14:
/usr/local/include/openssl/md5.h:49:27: note: declared here
   49 | OSSL_DEPRECATEDIN_3_0 int MD5_Init(MD5_CTX *c);
      |                           ^~~~~~~~
test_lib.c:763:2: error: ‘MD5_Update’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
  763 |  MD5_Update(&md5->md5_ctx, buf, len);
      |  ^~~~~~~~~~
In file included from test_lib.h:11,
                 from test_lib.c:14:
/usr/local/include/openssl/md5.h:50:27: note: declared here
   50 | OSSL_DEPRECATEDIN_3_0 int MD5_Update(MD5_CTX *c, const void *data, size_t len);
      |                           ^~~~~~~~~~
test_lib.c:764:2: error: ‘MD5_Final’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations]
  764 |  MD5_Final(md5->md, &md5->md5_ctx);
      |  ^~~~~~~~~
In file included from test_lib.h:11,
                 from test_lib.c:14:
/usr/local/include/openssl/md5.h:51:27: note: declared here
   51 | OSSL_DEPRECATEDIN_3_0 int MD5_Final(unsigned char *md, MD5_CTX *c);
      |                           ^~~~~~~~~
cc1: all warnings being treated as errors


  reply	other threads:[~2022-10-19 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  7:02 crypto/uadk: introduce uadk crypto driver Akhil Goyal
2022-10-17 14:02 ` Zhangfei Gao
2022-10-18 10:07   ` Zhangfei Gao
2022-10-18 10:52     ` Zhangfei Gao
2022-10-19  6:55       ` Thomas Monjalon
2022-10-19  7:24         ` Zhangfei Gao
2022-10-19 13:19 ` Zhangfei Gao
2022-10-19 14:25   ` Akhil Goyal [this message]
2022-10-19 15:27     ` [EXT] " Zhangfei Gao
2022-10-20  2:48       ` Zhangfei Gao

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=CO6PR18MB448421DD74F7F59E3EEE0349D82B9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=acc@openeuler.org \
    --cc=dev@dpdk.org \
    --cc=techboard@dpdk.org \
    --cc=zhangfei.gao@linaro.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.