From: zhoumin <zhoumin@loongson.cn>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Patrick Robb <probb@iol.unh.edu>
Subject: Re: [PATCH v3] build: automatically report minimum meson version
Date: Fri, 16 May 2025 19:28:04 +0800 [thread overview]
Message-ID: <a8bdadd1-57ac-b24f-8862-1d0166cab3be@loongson.cn> (raw)
In-Reply-To: <CAJFAV8ycKdFJgLBXr2RXcmUkHxftKywbrpOCvLtutRh6CMPujA@mail.gmail.com>
Hello David Marchand,
On Fri, May 16, 2025 at 3:33 PM, David Marchand wrote:
> Hello Min Zhou,
>
> On Thu, May 15, 2025 at 3:47 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
>> Add a script to buildtools to report the minimum meson version given in
>> our meson.build file. Then use this script in two ways:
>>
>> 1. in the .ci/linux-setup.sh script, use the auto-determined minimum
>> version to set up the CI, rather than hard-coding it.
>> 2. in meson.build call the script to report the version. This serves as
>> a sanity check to ensure that any changes to meson.build file do not
>> break the script.
>>
>> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>> Reviewed-by: Patrick Robb <probb@iol.unh.edu>
>>
>> ---
>> v3: update minimum meson to 0.57.2 (from 0.57.0) to fix CI errors
>> v2: rebase to latest main
> The LoongArch CI reported an error on this patch, but I can't find out
> the reason:
> https://mails.dpdk.org/archives/test-report/2025-May/877981.html
>
> This is probably related to the meson version in the build env, since
> this patch increases the minimum version to 0.57.2.
>
> Can you have a look please?
Sure. The reason for this error is related to the meson version in the
build environment. I will update the version of meson and retest this
patch.
>
next prev parent reply other threads:[~2025-05-16 11:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 15:24 [RFC PATCH] " Bruce Richardson
2024-10-09 16:40 ` Stephen Hemminger
2024-10-14 16:31 ` Patrick Robb
2025-05-13 8:59 ` [PATCH v2] " Bruce Richardson
2025-05-15 7:09 ` David Marchand
2025-05-15 9:36 ` Bruce Richardson
2025-05-15 11:39 ` David Marchand
2025-05-15 12:28 ` Patrick Robb
2025-05-15 12:54 ` Bruce Richardson
2025-05-15 13:46 ` [PATCH v3] " Bruce Richardson
2025-05-16 7:33 ` David Marchand
2025-05-16 11:28 ` zhoumin [this message]
2025-05-16 11:32 ` zhoumin
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=a8bdadd1-57ac-b24f-8862-1d0166cab3be@loongson.cn \
--to=zhoumin@loongson.cn \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.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).