From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 0/2] gcc-8 build fixes Date: Tue, 3 Apr 2018 10:23:43 +0100 Message-ID: <8988b191-30cd-a9fe-1cd2-8625c671a7fe@intel.com> References: <20180329170531.2478-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit To: Stephen Hemminger , dev@dpdk.org Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 4BD7C1B69B for ; Tue, 3 Apr 2018 11:23:46 +0200 (CEST) In-Reply-To: <20180329170531.2478-1-stephen@networkplumber.org> Content-Language: en-US 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 3/29/2018 6:05 PM, Stephen Hemminger wrote: > This fixes some of the obvious warnings found building DPDK > with gcc-8. There still are some deeper issues in the rte_hash_table > code; leave the fix for that up to the maintainer. > > Stephen Hemminger (2): > rte_mbuf: fix strncpy warnings > rte_metrics: fix strncpy truncation warning > > v3 > missing SOB on 1st patch > > v2 > fix issues with wrong length in mbuf pool_ops > don't need memset in metrics names > > Stephen Hemminger (2): > rte_mbuf: fix strncpy warnings > rte_metrics: fix strncpy truncation warning I tried with gcc-8 [1] and getting a few more build errors similar to these ones. Are these two files only build error you get? [1] gcc (GCC) 8.0.1 20180401 (experimental)