On Fri, 26 Jul 2024 12:34:25 -0400 Patrick Robb <pr...@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.
