From: Stephen Hemminger <stephen@networkplumber.org>
To: Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org, Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: How does CI system get updated?
Date: Fri, 26 Jul 2024 10:27:54 -0700 [thread overview]
Message-ID: <20240726102754.2a0f21ae@hermes.local> (raw)
In-Reply-To: <CAJvnSUB+rh=8-j5QWFB1OLFQ_iD_vng+9ZjDqpg-8uhWEi1exg@mail.gmail.com>
On Fri, 26 Jul 2024 12:34:25 -0400
Patrick Robb <probb@iol.unh.edu> wrote:
> Okay I understand better now how we ended up with an older mingw64
> version. The DPDK Docs for windows compile direct folks over to
> (https://sourceforge.net/projects/mingw-w64/files/) to get the
> prebuilt binaries, but the latest toolchain published there is Mingw64
> v8.*, whereas the current version is v11.*. So, when we upgraded to
> the "latest" published version, we upgraded to that v8.* from years
> ago. If you look at the mingw64 website downloads page
> (https://www.mingw-w64.org/downloads/), it directs people over to
> winlibs.com to download the prebuilt binaries for v11.
>
> I have replaced the Windows Server 2019 CI VM's old mingw64 binaries
> with the new (v11.*) ones downloaded from winlibs.com, and I see that
> Stephen's patch now passes the compile test. I can issue a retest for
> your series once I am all done making the update for the server 2022
> machine too.
>
> I guess this also raises the question of whether the DPDK docs for the
> windows mingw64 compile process should be updated to point to
> winlibs.com instead of sourceforge.net (only has the source code).
>
> https://doc.dpdk.org/guides/windows_gsg/build_dpdk.html#option-2-mingw-w64-toolchain
Yes, projects move we need to keep links up to date.
prev parent reply other threads:[~2024-07-26 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 14:55 How does CI system get updated? Stephen Hemminger
2024-07-25 19:06 ` Patrick Robb
2024-07-26 16:34 ` Patrick Robb
2024-07-26 17:27 ` Stephen Hemminger [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=20240726102754.2a0f21ae@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=probb@iol.unh.edu \
--cc=roretzla@linux.microsoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.