From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 58FC0A3296 for ; Wed, 23 Oct 2019 12:15:37 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id AA82E1C031; Wed, 23 Oct 2019 12:15:36 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id A210F9E4; Wed, 23 Oct 2019 12:15:35 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2019 03:15:34 -0700 X-IronPort-AV: E=Sophos;i="5.68,220,1569308400"; d="scan'208";a="188206888" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.95]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Oct 2019 03:15:33 -0700 Date: Wed, 23 Oct 2019 11:15:30 +0100 From: Bruce Richardson To: bugzilla@dpdk.org Cc: dev@dpdk.org Message-ID: <20191023101530.GA482@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Subject: Re: [dpdk-dev] [Bug 355] Meson build failure X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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