On Tue, May 5, 2020 at 6:32 PM David Christensen <d...@linux.vnet.ibm.com> wrote: > >> diff --git a/lib/librte_eal/ppc/include/rte_memcpy.h > >> b/lib/librte_eal/ppc/include/rte_memcpy.h > >> index 25311ba1d..de47a5d2e 100644 > >> --- a/lib/librte_eal/ppc/include/rte_memcpy.h > >> +++ b/lib/librte_eal/ppc/include/rte_memcpy.h > >> @@ -8,8 +8,8 @@ > >> > >> #include <stdint.h> > >> #include <string.h> > >> -/*To include altivec.h, GCC version must >= 4.8 */ > >> -#include <altivec.h> > >> +#include "rte_altivec.h" > >> +#include "rte_common.h" > > > > I can't find "rte_altivec.h", am I missing something. > > > > With just ignoring "-Warray-bounds" changes, I confirm ena build issue is > > fixed > > with gcc 9.1 > > The rte_altivec.h is related to another open patch required to build on > POWER systems (http://patches.dpdk.org/patch/69605/) that's waiting to > be accepted. You may not have encountered it if you're not building the > MLX5 PMD which has additional library requirements.
Is there a point in having two patches? -- David Marchand
