From: David Marchand <david.marchand@redhat.com>
To: dpdklab <dpdklab@iol.unh.edu>, Min Zhou <zhoumin@loongson.cn>
Cc: dev@dpdk.org, mb@smartsharesystems.com, thomas@monjalon.net,
ci@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH 0/5] Increase minimum meson version
Date: Tue, 8 Oct 2024 10:28:25 +0200 [thread overview]
Message-ID: <CAJFAV8yLWLMtOYQHvfO3bqD-RPKEXPn0aop+7Y=uWd09CDa9Nw@mail.gmail.com> (raw)
In-Reply-To: <20240920125737.1197969-1-bruce.richardson@intel.com>
Hello CI guys,
On Fri, Sep 20, 2024 at 2:57 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> This patchset proposed increasing the minimum meson version to 0.57
> and makes changes to update our build files appropriately for that
> change: replacing deprecated functions, removing unnecessary version
> checks and taking advantage of some new capabilities.
>
> Why 0.57? No one particular reason; it's mainly a conservative version
> bump that doesn't have many impacts, but still gives us the minimum
> updates we need to replace the deprecated get_cross_properties fn
> and have a few extra features guaranteed available.
>
> Bruce Richardson (5):
> build: increase minimum meson version to 0.57
> build: remove version check on compiler links function
> build: remove unnecessary version checks
> build: use version file support from meson
> build: replace deprecated meson function
>
> .ci/linux-setup.sh | 2 +-
> config/arm/meson.build | 4 ++--
> config/meson.build | 8 ++++----
> config/riscv/meson.build | 4 ++--
> doc/api/meson.build | 2 +-
> doc/guides/linux_gsg/sys_reqs.rst | 2 +-
> doc/guides/prog_guide/build-sdk-meson.rst | 2 +-
> drivers/common/qat/meson.build | 2 +-
> drivers/crypto/ipsec_mb/meson.build | 2 +-
> drivers/event/cnxk/meson.build | 2 +-
> drivers/meson.build | 7 ++-----
> drivers/net/cnxk/meson.build | 2 +-
> lib/meson.build | 6 ------
> meson.build | 7 ++-----
> 14 files changed, 20 insertions(+), 32 deletions(-)
This series can't be merged until the (UNH and LoongArch) CI are ready
for such a change.
TL;DR: the meson minimum version is being changed from 0.53.2 to 0.57
in the current release.
@UNH @Min Zhou
How long would it take for all CI to be ready for this change?
Important note: if relevant to your CI, testing against LTS branches
must still be done with the 0.53.2 version, so no change relying on
post 0.53.2 meson feature gets backported.
--
David Marchand
next parent reply other threads:[~2024-10-08 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240920125737.1197969-1-bruce.richardson@intel.com>
2024-10-08 8:28 ` David Marchand [this message]
2024-10-08 19:49 ` [OS-Team] [dpdklab] " Patrick Robb
2024-10-08 20:04 ` Bruce Richardson
2024-10-09 14:27 ` Patrick Robb
2024-10-09 1:04 ` zhoumin
2024-10-09 14:31 ` Patrick Robb
2024-10-14 1:24 ` zhoumin
2024-10-16 13:08 ` Patrick Robb
2024-10-17 5:26 ` Patrick Robb
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='CAJFAV8yLWLMtOYQHvfO3bqD-RPKEXPn0aop+7Y=uWd09CDa9Nw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=mb@smartsharesystems.com \
--cc=thomas@monjalon.net \
--cc=zhoumin@loongson.cn \
/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).