DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Subject: Re: [PATCH] build: bump meson version to remove warnings
Date: Fri, 5 Dec 2025 12:28:17 +0000	[thread overview]
Message-ID: <aTLP4TBHLtqm0kpR@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251205121301.3443561-1-bruce.richardson@intel.com>

On Fri, Dec 05, 2025 at 12:13:01PM +0000, Bruce Richardson wrote:
> The build of DPDK now uses features from version 0.6 of meson, which is
> greater than the current minimum of 0.57.2. Although these features are
> non-critical, they do cause warnings to be emitted on build. Increase
> minimum meson version to 0.61 (== version in Ubuntu 22.04 LTS) to remove
> these warnings.
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
>  meson.build | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
With this patch, and the previously submitted patchset for assigning test
cases to the various categories/suites, all warnings in the meson
configuration stage should now be gone.

In terms of the specific version, as noted above I chose the version of
meson present in Ubuntu 22.04 as a reasonable baseline. Both debian stable,
and debian old-stable have newer versions than that in them. For the RHEL
line, I'm not sure what the baseline is, but I believe that RHEL 8 shipped
originally with a meson version even older than 0.57, so moving to a later
one I hope doesn't matter. [I wasn't easily able to find out from Google
what the current meson version in RHEL 8/9/10 is]

Regards,
/Bruce

      reply	other threads:[~2025-12-05 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 12:13 Bruce Richardson
2025-12-05 12:28 ` Bruce Richardson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aTLP4TBHLtqm0kpR@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).