On Thu, Nov 15, 2018 at 05:36:06PM +0000, Burdick, Cliff wrote: > > > -----Original Message----- > From: Bruce Richardson [mailto:bruce.richard...@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 > <snip> > > 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
