[dpdk-dev] [Bug 355] Meson build failure

[Bruce Richardson]

On Tue, Oct 22, 2019 at 06:45:30PM +0000, bugzilla at dpdk.org wrote:
> https://bugs.dpdk.org/show_bug.cgi?id=355
> 
>             Bug ID: 355
>            Summary: Meson build failure
>            Product: DPDK
>            Version: unspecified
>           Hardware: ARM
>                 OS: Linux
>             Status: UNCONFIRMED
>           Severity: major
>           Priority: Normal
>          Component: meson
>           Assignee: dev at dpdk.org
>           Reporter: dharmik.thakkar at arm.com
>   Target Milestone: ---
> 
> Meson build fails on master (19.11.0-rc0).
> Architecture: aarch64
> GCC 8.3.0
> Ubuntu 18.04
> 
> Error:
> 
> In file included from ../drivers/net/bnx2x/bnx2x.h:22,
>                  from ../drivers/net/bnx2x/bnx2x_ethdev.c:8:
> ../drivers/net/bnx2x/bnx2x_osal.h:27:17: error: conflicting types for
> ‘uint64_t’
>  #define __le64  uint64_t
>                  ^~~~~~~~
> In file included from /usr/include/stdint.h:37,
>                  from /usr/lib/gcc/aarch64-linux-gnu/8/include/stdint.h:9,
>                  from
> ../lib/librte_eal/common/include/arch/arm/rte_byteorder.h:16,
>                  from ../drivers/net/bnx2x/bnx2x.h:17,
>                  from ../drivers/net/bnx2x/bnx2x_ethdev.c:8:
> /usr/include/aarch64-linux-gnu/bits/stdint-uintn.h:27:20: note: previous
> declaration of ‘uint64_t’ was here
>  typedef __uint64_t uint64_t;
>                     ^~~~~~~~

Not sure it's correct to classify this as a build system bug. The build
system looks to be behaving correctly here, it's just the code has
redefined one of the standard int types and the compiler is flagging the
error. Suggest the component should be changed to the "bnx2x" driver rather
than just blaming meson. :-)

/Bruce