dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: bugzilla@dpdk.org
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [Bug 355] Meson build failure
Date: Wed, 23 Oct 2019 11:15:30 +0100	[thread overview]
Message-ID: <20191023101530.GA482@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <bug-355-3@http.bugs.dpdk.org/>

On Tue, Oct 22, 2019 at 06:45:30PM +0000, bugzilla@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@dpdk.org
>           Reporter: dharmik.thakkar@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

  reply	other threads:[~2019-10-23 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 18:45 [dpdk-dev] [Bug 355] Meson build failure bugzilla
2019-10-23 10:15 ` Bruce Richardson [this message]
2019-12-02 17:14 ` [dpdk-dev] [Bug 355] Meson build failure due to libibverbs-dev upgrade (version=45mlnx1-1.45101) bugzilla

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=20191023101530.GA482@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bugzilla@dpdk.org \
    --cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).