From: Andre Muezerie <andremue@linux.microsoft.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: stephen@networkplumber.org, dev@dpdk.org, dmitry.kozliuk@gmail.com
Subject: Re: [PATCH v5] doc: modernize build instructions on Windows
Date: Mon, 11 Nov 2024 07:59:00 -0800 [thread overview]
Message-ID: <20241111155900.GA26210@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <6195955.yaVYbkx8dN@thomas>
On Mon, Nov 11, 2024 at 03:11:03PM +0100, Thomas Monjalon wrote:
> 31/10/2024 04:08, Andre Muezerie:
> > -Required version is Meson 0.57.
> > -
> > -Versions starting from 0.58 are unusable with LLVM toolchain
> > -because of a `Meson issue <https://github.com/mesonbuild/meson/issues/8981>`_.
> > +Meson version 1.5.2 or newer is recommended.
>
> I would prefer to know which minimal version is supported.
> Giving the latest version is not so helpful.
>
> PS: when sending a new version, please reply to the very first version
> to avoid excessive indent in mail list, thanks.
>
>
Sorry for the late reply.
The Meson issue previously mentioned in the documentation took a significant
amount of time to get fixed. The fix only showed up in the main tree on August 7:
https://github.com/mesonbuild/meson/pull/11715#event-13793516174
Meson 1.5.2 was the first release containing that fix:
https://github.com/mesonbuild/meson/releases
That's the reason we added that specific version information to the patch, not
just because it was the newest. But I see how it looked like that was the reason.
I'll change the wording a little to make it more clear, and reply to the first version
as suggested.
Thanks for all the suggestions. They are greatly appreciated.
next prev parent reply other threads:[~2024-11-11 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 14:15 [PATCH] doc: enhance build instructions on windows Andre Muezerie
2024-10-25 14:15 ` [PATCH] doc: enhanced build instructions on Windows Andre Muezerie
2024-10-25 14:50 ` Thomas Monjalon
2024-10-25 19:30 ` [PATCH v2 0/2] doc: enhance build instructions on windows Andre Muezerie
2024-10-25 19:30 ` [PATCH v2 1/2] doc: enhanced build instructions on Windows Andre Muezerie
2024-10-26 21:03 ` Dmitry Kozlyuk
2024-10-28 19:45 ` [PATCH v3] doc: enhance " Andre Muezerie
2024-10-30 9:09 ` Dmitry Kozlyuk
2024-10-30 15:19 ` [PATCH v4] doc: modernize " Andre Muezerie
2024-10-30 15:48 ` Stephen Hemminger
2024-10-31 3:08 ` [PATCH v5] " Andre Muezerie
2024-11-11 14:11 ` Thomas Monjalon
2024-11-11 15:59 ` Andre Muezerie [this message]
2024-10-25 19:30 ` [PATCH v2 2/2] doc: provide Meson version that works Andre Muezerie
2024-10-26 20:45 ` Dmitry Kozlyuk
2024-11-11 16:14 ` [PATCH v6] doc: modernize build instructions on Windows Andre Muezerie
2024-11-11 18:18 ` Thomas Monjalon
2024-11-12 9:56 ` Dmitry Kozlyuk
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=20241111155900.GA26210@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).