The warning messages are deprecated APIs warnings from openssl , not compiler warnings from gcc, the integrity of DPDK remain the same. Alongside openssl pmd, the ccp and qat pmd also raise the same type of warnings once openssl 3.0 installed.
In the current intel roadmap, we will try to support 3.0 API fully for openssl and qat pmds by the end of year, so this patch is the first step. I think the warning messages are safe to stay, Unfortunately the fix ccp pmd driver is out of our reach. Regards Kai > -----Original Message----- > From: Akhil Goyal <gak...@marvell.com> > Sent: Friday, February 25, 2022 3:56 AM > To: Ji, Kai <kai...@intel.com>; dev@dpdk.org > Cc: Zhang, Roy Fan <roy.fan.zh...@intel.com> > Subject: RE: [EXT] [dpdk-dev v5] crypto/openssl: openssl 3.0 support on sym > crypto routine > > Hi Kai, > > Hi Akhil, > > > > This patch was intend to support Openssl 3.0 on symmetric crypto > > algorithms only, where the deprecated APIs, compile warnings and > > failing test cases were fixed. > > All the asymmetric crypto related issues stay untreated and will be > > fixed in the next patch. > > > How can one verify if the driver is openssl 3.0 compliant? > Is there a way to bypass those warnings? > We cannot have build with warnings or we can have something in meson.build to > bypass those for openssl pmd.
