[PATCH] build: bump meson version to remove warnings

[PATCH] build: bump meson version to remove warnings

[Bruce Richardson]

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(-)

diff --git a/meson.build b/meson.build
index b01010ffa0..6b8cfa8b2e 100644
--- a/meson.build
+++ b/meson.build
@@ -10,7 +10,7 @@ project('DPDK', 'c',
             'default_library=static',
             'warning_level=2',
         ],
-        meson_version: '>= 0.57.2'
+        meson_version: '>= 0.61'
         # meson_version_windows: '>= 1.5.2'
 )
 
-- 
2.51.0

Re: [PATCH] build: bump meson version to remove warnings

[Bruce Richardson]

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

Re: [PATCH] build: bump meson version to remove warnings

[David Marchand]

Hello,

On Fri, 5 Dec 2025 at 13:28, Bruce Richardson
<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 <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

Re: [PATCH] build: bump meson version to remove warnings

[Patrick Robb]

[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]

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.

On Tue, Jan 20, 2026 at 3:32 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hello,
>
> On Fri, 5 Dec 2025 at 13:28, Bruce Richardson
> <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 <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
>
>

[-- Attachment #2: Type: text/html, Size: 2613 bytes --]

Re: [PATCH] build: bump meson version to remove warnings

[Bruce Richardson]

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

Re: [PATCH] build: bump meson version to remove warnings

[Patrick Robb]

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

On Fri, Jan 23, 2026 at 4:02 AM Bruce Richardson <bruce.richardson@intel.com>
wrote:

> 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.
>

Right now we do build new images any time any DPDK dependencies are
updated, including meson. That's done with the dpdk-ci template engine (an
application that templates out Dockerfiles for DPDK CI testing):
https://git.dpdk.org/tools/dpdk-ci/tree/containers

However, to simplify we can just move to installing meson at runtime in all
cases. We already have to do this sometimes (like when testing with an LTS
that requires a different meson) so doing it in all cases wouldn't be too
disruptive. And, of course the main point is that that would allow us to
accomodate a version bump like this  without rebuilding the CI images. Let
me know if you have an opinion. In any case I will chat with the CI Lab
students about it.

[-- Attachment #2: Type: text/html, Size: 1772 bytes --]

Re: [PATCH] build: bump meson version to remove warnings

[Bruce Richardson]

On Fri, Jan 23, 2026 at 10:35:53AM -0500, Patrick Robb wrote:
>    On Fri, Jan 23, 2026 at 4:02 AM Bruce Richardson
>    <[1]bruce.richardson@intel.com> wrote:
> 
>      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.
> 
>    Right now we do build new images any time any DPDK dependencies are
>    updated, including meson. That's done with the dpdk-ci template engine
>    (an application that templates out Dockerfiles for DPDK CI
>    testing): [2]https://git.dpdk.org/tools/dpdk-ci/tree/containers
>    However, to simplify we can just move to installing meson at runtime in
>    all cases. We already have to do this sometimes (like when testing with
>    an LTS that requires a different meson) so doing it in all cases
>    wouldn't be too disruptive. And, of course the main point is that that
>    would allow us to accomodate a version bump like this  without
>    rebuilding the CI images. Let me know if you have an opinion. In any
>    case I will chat with the CI Lab students about it.
> 
Having it installed at runtime would be definitely good.

The other thing I was considering is whether we actually need to use the
minimum meson version for all build testing. If one or two containers have
the minimum version that should be fine, and others can use the distro
supplied version so long as its >= minimum.

/Bruce

Re: [PATCH] build: bump meson version to remove warnings

[Patrick Robb]

[-- Attachment #1: Type: text/plain, Size: 2349 bytes --]

On Fri, Jan 23, 2026 at 10:43 AM Bruce Richardson <
bruce.richardson@intel.com> wrote:

> On Fri, Jan 23, 2026 at 10:35:53AM -0500, Patrick Robb wrote:
> >    On Fri, Jan 23, 2026 at 4:02 AM Bruce Richardson
> >    <[1]bruce.richardson@intel.com> wrote:
> >
> >      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.
> >
> >    Right now we do build new images any time any DPDK dependencies are
> >    updated, including meson. That's done with the dpdk-ci template engine
> >    (an application that templates out Dockerfiles for DPDK CI
> >    testing): [2]https://git.dpdk.org/tools/dpdk-ci/tree/containers
> >    However, to simplify we can just move to installing meson at runtime
> in
> >    all cases. We already have to do this sometimes (like when testing
> with
> >    an LTS that requires a different meson) so doing it in all cases
> >    wouldn't be too disruptive. And, of course the main point is that that
> >    would allow us to accomodate a version bump like this  without
> >    rebuilding the CI images. Let me know if you have an opinion. In any
> >    case I will chat with the CI Lab students about it.
> >
> Having it installed at runtime would be definitely good.
>
> The other thing I was considering is whether we actually need to use the
> minimum meson version for all build testing. If one or two containers have
> the minimum version that should be fine, and others can use the distro
> supplied version so long as its >= minimum.


Okay, both of the options above sound good. From my end if I had to choose
I would just do the first solution (install meson at runtime in all cases)
because it keeps our process uniform across distro testing and there is no
"special" container. But, the second option sounds good too so please let
me know what you think is best.


>


> /Bruce
>

[-- Attachment #2: Type: text/html, Size: 3383 bytes --]

Re: [PATCH] build: bump meson version to remove warnings

[Bruce Richardson]

On Fri, Jan 23, 2026 at 10:59:23AM -0500, Patrick Robb wrote:
>    On Fri, Jan 23, 2026 at 10:43 AM Bruce Richardson
>    <[1]bruce.richardson@intel.com> wrote:
> 
>      On Fri, Jan 23, 2026 at 10:35:53AM -0500, Patrick Robb wrote:
>      >    On Fri, Jan 23, 2026 at 4:02 AM Bruce Richardson
>      >    <[1][2]bruce.richardson@intel.com> wrote:
>      >
>      >      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.
>      >
>      >    Right now we do build new images any time any DPDK dependencies
>      are
>      >    updated, including meson. That's done with the dpdk-ci template
>      engine
>      >    (an application that templates out Dockerfiles for DPDK CI
>      >    testing):
>      [2][3]https://git.dpdk.org/tools/dpdk-ci/tree/containers
>      >    However, to simplify we can just move to installing meson at
>      runtime in
>      >    all cases. We already have to do this sometimes (like when
>      testing with
>      >    an LTS that requires a different meson) so doing it in all
>      cases
>      >    wouldn't be too disruptive. And, of course the main point is
>      that that
>      >    would allow us to accomodate a version bump like this  without
>      >    rebuilding the CI images. Let me know if you have an opinion.
>      In any
>      >    case I will chat with the CI Lab students about it.
>      >
>      Having it installed at runtime would be definitely good.
>      The other thing I was considering is whether we actually need to use
>      the
>      minimum meson version for all build testing. If one or two
>      containers have
>      the minimum version that should be fine, and others can use the
>      distro
>      supplied version so long as its >= minimum.
> 
>    Okay, both of the options above sound good. From my end if I had to
>    choose I would just do the first solution (install meson at runtime in
>    all cases) because it keeps our process uniform across distro testing
>    and there is no "special" container. But, the second option sounds good
>    too so please let me know what you think is best.
> 

Go with your runtime solution, it's fine - and possibly better.

Re: [PATCH] build: bump meson version to remove warnings

[Kevin Traynor]

On 05/12/2025 12:28, Bruce Richardson 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 <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]
> 

fyi - RHEL-9 has 0.63.3, RHEL-10 has 1.4.1

> Regards,
> /Bruce
> 

Re: [PATCH] build: bump meson version to remove warnings

[Bruce Richardson]

On Wed, Jan 28, 2026 at 11:19:16AM +0000, Kevin Traynor wrote:
> On 05/12/2025 12:28, Bruce Richardson 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 <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]
> > 
> 
> fyi - RHEL-9 has 0.63.3, RHEL-10 has 1.4.1
> 
Perfect, thanks for confirming. So 0.61 min seems fine then for RHEL instances.

/Bruce

Re: [PATCH] build: bump meson version to remove warnings

[Patrick Robb]

On Fri, Jan 23, 2026 at 11:11 AM Bruce Richardson
<bruce.richardson@intel.com> wrote:
.
> >
> >    Okay, both of the options above sound good. From my end if I had to
> >    choose I would just do the first solution (install meson at runtime in
> >    all cases) because it keeps our process uniform across distro testing
> >    and there is no "special" container. But, the second option sounds good
> >    too so please let me know what you think is best.
> >
>
> Go with your runtime solution, it's fine - and possibly better.

I realized after looking at our scripting that I pushed a change last
year that does the "meet meson version at runtime based on the output
of buildtools/get-min-meson-version.py" last year. That was probably
when you originally added buildtools/get-min-meson-version.py. So, I
guess we can say that no coordination with the UNH group is needed
when the meson version is bumped in the future. The same should be
true for the other labs because as far as I know they are using
dpdk/.ci/linux-setup.sh for their CI jobs, but also it definitely
doesn't hurt to ping the ci@dpdk.org mailing list when these updates
happen in the future anyways. Thanks.