DPDK CI discussions
 help / color / mirror / Atom feed
From: Jie Zhou <jizh@microsoft.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Cc: thomas <thomas@monjalon.net>, Tyler Retzlaff <roretzla@microsoft.com>
Subject: Re: [dpdk-ci] Update the meson used in CI pipeline
Date: Thu, 4 Mar 2021 17:23:11 +0000	[thread overview]
Message-ID: <BY5PR21MB14261690A865BB5150625021D0979@BY5PR21MB1426.namprd21.prod.outlook.com> (raw)
In-Reply-To: <BY5PR21MB1426C5DD8AD75704008E38EED09F9@BY5PR21MB1426.namprd21.prod.outlook.com>

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

Just follow up to see if the CI pipeline already stated using 0.57.0 for Windows DPDK?

Thanks.

Jie

From: Jie Zhou
Sent: Wednesday, February 24, 2021 3:50 PM
To: ci@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>; Tyler Retzlaff <roretzla@microsoft.com>
Subject: Update the meson used in CI pipeline

Hi,
At porting testpmd, discovered that on Windows, meson has a bug which generates incorrect linker flag "--subsystem,console" instead of "/subsystem:console" and will fail the DPDK build on Windows. Meson 0.57.0 has the fix and should be used for DPDK Windows build.
Can your team please help update the meson used in CI pipeline?
Thanks!
Jie
P.S.
The DPDK WindowsGSG document meson version update is tracked by WindowsGSGDoc: Update the meson version to use for Windows DPDK - Patchwork<http://patchwork.dpdk.org/project/dpdk/patch/1614209812-4331-1-git-send-email-jizh@linux.microsoft.com/>.

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

      reply	other threads:[~2021-03-04 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 23:50 Jie Zhou
2021-03-04 17:23 ` Jie Zhou [this message]

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=BY5PR21MB14261690A865BB5150625021D0979@BY5PR21MB1426.namprd21.prod.outlook.com \
    --to=jizh@microsoft.com \
    --cc=ci@dpdk.org \
    --cc=roretzla@microsoft.com \
    --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).