From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH 1/1] eal: Don't fail secondary if primary is missing tailqs Date: Fri, 16 Nov 2018 10:22:23 +0000 Message-ID: <20181116102222.GA3144@bricha3-MOBL.ger.corp.intel.com> References: <1542219312.11515.15.camel@debian.org> <03A7D9A58FAFB54FBB01FEE199D7308A0134B8FB80@wdc1exchmbxp02.hq.corp.viasat.com> <1542274397.11515.18.camel@debian.org> <03A7D9A58FAFB54FBB01FEE199D7308A0134B905F7@wdc1exchmbxp02.hq.corp.viasat.com> <20181115164116.GA5012@bricha3-MOBL.ger.corp.intel.com> <03A7D9A58FAFB54FBB01FEE199D7308A0134B90649@wdc1exchmbxp02.hq.corp.viasat.com> <59AF69C657FD0841A61C55336867B5B0726E0748@IRSMSX103.ger.corp.intel.com> <1542301516.11515.21.camel@debian.org> <20181115171724.GA14632@bricha3-MOBL.ger.corp.intel.com> <03A7D9A58FAFB54FBB01FEE199D7308A0134B90731@wdc1exchmbxp02.hq.corp.viasat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Luca Boccassi , Thomas Monjalon , "Burakov, Anatoly" , "dev@dpdk.org" To: "Burdick, Cliff" Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 2415A29C6 for ; Fri, 16 Nov 2018 11:22:27 +0100 (CET) Content-Disposition: inline In-Reply-To: <03A7D9A58FAFB54FBB01FEE199D7308A0134B90731@wdc1exchmbxp02.hq.corp.viasat.com> 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 Thu, Nov 15, 2018 at 05:36:06PM +0000, Burdick, Cliff wrote: > > > -----Original Message----- > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > Sent: Thursday, November 15, 2018 9:17 AM > To: Luca Boccassi > Cc: Burdick, Cliff; Thomas Monjalon; Burakov, Anatoly; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 1/1] eal: Don't fail secondary if primary is missing tailqs > > > Bumping the minimum version would be really nice generally for DPDK, but I > > don't think this is the point in the release cycle to do so. I need to try > > and track down why this is broken with older mesons - most version specific > > things are harmless, and I'd like to keep it that way! > > > > If we can't fix this in rc4, then document, I suggest. That way we don't > > require absolutely everyone to use bleeding-edge meson. > > > > /Bruce > > Hi Bruce and Luca, that seems to have fixed the problem. It appears that Meson > was warning about having a new version anyways since you're using newer features. 0.45 > did not warn, but 0.48 appears to check a version->feature map: > > WARNING: Project specifies a minimum meson_version '>= 0.41' but uses features which were added in newer versions: > * 0.42.0: {'extra_cflags arg in pkgconfig.generate'} > * 0.46.0: {'recursive arg in extract_all_objects'} > * 0.48.0: {'console arg in custom_target'} > Found ninja-1.8.2 at /usr/bin/ninja > > Thanks for resolving it! Glad to hear it's fixed for you. /Bruce