From: Bruce Richardson <bruce.richardson@intel.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>,
<ci@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Aaron Conole <aconole@redhat.com>,
Luca Boccassi <luca.boccassi@gmail.com>,
Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: [PATCH] build: bump meson version to remove warnings
Date: Fri, 23 Jan 2026 09:02:36 +0000 [thread overview]
Message-ID: <aXM5LAcV6EC6L9VS@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAJvnSUC3ze51WFHx=cRMGKezrwXvo7fCXH8o64qJsbWf9SXsZg@mail.gmail.com>
On Thu, Jan 22, 2026 at 01:59:19PM -0500, Patrick Robb wrote:
> Thanks David for the CC. We need to rebuild all of our DPDK
> container images for the distro build testing etc. which takes some
> time. We should be ready early next week.
>
Is rebuilding all container images something that needs to be done every
time we do a minimum meson version bump? If so, we probably need to look to
take steps to make things easier to do.
/Bruce
> On Tue, Jan 20, 2026 at 3:32 AM David Marchand
> <[1]david.marchand@redhat.com> wrote:
>
> Hello,
> On Fri, 5 Dec 2025 at 13:28, Bruce Richardson
> <[2]bruce.richardson@intel.com> wrote:
> >
> > 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 <[3]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]
> Cc: Timothy for .rpm distributions, Luca for .deb.
> I prefer we get some acks from distributions people.
> Also, this patch requires coordination with the CI guys (as can be
> seen in patchwork, many envs are using old versions of meson).
> --
> David Marchand
>
> References
>
> 1. mailto:david.marchand@redhat.com
> 2. mailto:bruce.richardson@intel.com
> 3. mailto:bruce.richardson@intel.com
next prev parent reply other threads:[~2026-01-23 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 12:13 [PATCH] build: bump meson version to remove warnings Bruce Richardson
2025-12-05 12:28 ` Bruce Richardson
2026-01-20 8:31 ` David Marchand
2026-01-22 18:59 ` Patrick Robb
2026-01-23 9:02 ` Bruce Richardson [this message]
2026-01-23 15:35 ` Patrick Robb
2026-01-23 15:43 ` Bruce Richardson
2026-01-23 15:59 ` Patrick Robb
2026-01-23 16:11 ` Bruce Richardson
2026-02-03 20:55 ` Patrick Robb
2026-01-28 11:19 ` Kevin Traynor
2026-01-28 11:37 ` Bruce Richardson
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=aXM5LAcV6EC6L9VS@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=tredaelli@redhat.com \
/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