> Hi, Akhil
>
> On Mon, 30 Jun 2025 at 17:04, Akhil Goyal <gak...@marvell.com> wrote:
> >
> > > > > make[2]: Entering directory '/home/gakhil/up/uadk'
> > > > > depbase=`echo wd_alg.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\
> > > > > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -
> > > Wall -Werror -fno-strict-aliasing -I./include -fPIC -fPIE -pie
> > > -fstack-protector-
> > > strong -D_FORTIFY_SOURCE=2 -O2 -ftrapv -Wl,-z,relro,-z,now -Wl,-s -
> > > DUADK_VERSION_NUMBER="\"UADK version: 2.9.0\"" -
> > > DUADK_RELEASED_TIME="\"Released June 6, 2025\"" -g -O2 -MT wd_alg.lo
> -
> > > MD -MP -MF $depbase.Tpo -c -o wd_alg.lo wd_alg.c &&\
> > > > > mv -f $depbase.Tpo $depbase.Plo
> > > > > libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -Werror -fno-strict-
> aliasing
> > > -I./include -fPIC -fstack-protector-strong -D_FORTIFY_SOURCE=2 -O2 -ftrapv
> -
> > > Wl,-z,relro,-z,now -Wl,-s "-DUADK_VERSION_NUMBER=\"UADK version:
> 2.9.0\""
> > > "-DUADK_RELEASED_TIME=\"Released June 6, 2025\"" -g -O2 -MT wd_alg.lo
> -
> > > MD -MP -MF .deps/wd_alg.Tpo -c wd_alg.c -fPIC -DPIC -o .libs/wd_alg.o
> > > > > wd_alg.c: In function ‘wd_check_ce_support’:
> > > > > wd_alg.c:106:44: error: ‘HWCAP_CE_SM3’ undeclared (first use in this
> > > function)
> > > > > 106 | if (!strcmp("sm3", alg_name) && (hwcaps & HWCAP_CE_SM3))
> > > > > | ^~~~~~~~~~~~
> > > > > wd_alg.c:106:44: note: each undeclared identifier is reported only
> > > > > once
> for
> > > each function it appears in
> > > > > wd_alg.c:115:46: error: ‘HWCAP_CE_SM4’ undeclared (first use in this
> > > function)
> > > > > 115 | if (!strcmp("(sm4)", alg_tail) && (hwcaps & HWCAP_CE_SM4))
> > > > > | ^~~~~~~~~~~~
> > > > > wd_alg.c: In function ‘wd_check_sve_support’:
> > > > > wd_alg.c:128:15: error: ‘HWCAP_SVE’ undeclared (first use in this
> function)
> > > > > 128 | if (hwcaps & HWCAP_SVE)
> > > > > | ^~~~~~~~~
> > > > > make[2]: *** [Makefile:1055: wd_alg.lo] Error 1
> > >
> > > This is solved by https://github.com/Linaro/uadk/pull/679
> > > Will be merged next week.
> >
> > So are you going to update this patchset with newer version of uadk?
>
> How bout just adding bug fix patches on master branch.
> or have to ensure the dependent uadk release version build no problem
> on both x86 and Arm?
How is the DPDK user supposed to build your driver without proper tag of uadk?
May be apply a hot fix tag(2.9.1 or something) on UADK and mention that in your
driver doc.
You need to ensure when someone picks a particular DPDK release,
your driver can be built with the version mentioned in your PMD doc.
>
> It's our mistake that we ignored x86 platform.
