From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 808F4A0AC5 for ; Wed, 1 May 2019 16:24:48 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B15B0293B; Wed, 1 May 2019 16:24:47 +0200 (CEST) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 94DD3DE3 for ; Wed, 1 May 2019 16:24:45 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 May 2019 07:24:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,418,1549958400"; d="scan'208";a="147375374" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.48]) by fmsmga007.fm.intel.com with SMTP; 01 May 2019 07:24:42 -0700 Received: by (sSMTP sendmail emulation); Wed, 01 May 2019 15:24:41 +0100 Date: Wed, 1 May 2019 15:24:41 +0100 From: Bruce Richardson To: dev@dpdk.org Message-ID: <20190501142440.GA1807@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline User-Agent: Mutt/1.11.4 (2019-03-13) Subject: [dpdk-dev] Compiling on Fedora 30 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" Message-ID: <20190501142441.pQjnUY_hGTutx76EyB4O5kq_vdNRtaGIu8Myba639SU@z> Hi, Just an FYI for anyone updating to Fedora 30, released this week; there are issues with building latest DPDK head. F30 seems to ship with GCC 9, which is not officially released yet as far as I can see, and so has some new warnings being flagged in our code. I needed to set the following cflags to enable a clean build of DPDK on my F30 system: "-Wno-address-of-packed-member -Wno-format-overflow -Wno-maybe-uninitialized" Hopefully, we can get these warnings closed off before 19.05, but just want to flag this in advance for anyone who is updating soon. Regards, /Bruce