From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC] doc: update required Mingw version
Date: Wed, 13 Mar 2024 15:07:10 -0700 [thread overview]
Message-ID: <20240313220815.20998-1-stephen@networkplumber.org> (raw)
Add a required version for mingw. The version is selected is
the version available for Debian oldstable (Bullseye) as listed on:
https://www.mingw-w64.org/downloads/
The 10.0 version was released in 4/4/2022,
The current upstream version 11.0.
Also drop note about Ubuntu 16.04 because that release is EOL
and the if using a current version of Ubuntu, the package will
not be a problem.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/windows_gsg/build_dpdk.rst | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/doc/guides/windows_gsg/build_dpdk.rst b/doc/guides/windows_gsg/build_dpdk.rst
index 1b6d3a650a49..708875c16f8e 100644
--- a/doc/guides/windows_gsg/build_dpdk.rst
+++ b/doc/guides/windows_gsg/build_dpdk.rst
@@ -11,7 +11,7 @@ Building the DPDK and its applications requires one of the following
environments:
* LLVM 14.0.0 (or later) and Microsoft MSVC linker.
-* The MinGW-w64 toolchain (either native or cross).
+* The MinGW-w64 10.0 (or later) toolchain (either native or cross).
* Microsoft Visual Studio 2022 (any edition).
- note Microsoft Visual Studio 2022 does not currently build enough
@@ -49,10 +49,6 @@ and ensure the Windows SDK is selected.
Option 2. MinGW-w64 Toolchain
-----------------------------
-On Linux, i.e. for cross-compilation, install MinGW-w64 via a package manager.
-Version 4.0.4 for Ubuntu 16.04 cannot be used due to a
-`MinGW-w64 bug <https://sourceforge.net/p/mingw-w64/bugs/562/>`_.
-
On Windows, obtain the latest version installer from
`MinGW-w64 repository <https://sourceforge.net/projects/mingw-w64/files/>`_.
Any thread model (POSIX or Win32) can be chosen, DPDK does not rely on it.
--
2.43.0
reply other threads:[~2024-03-13 22:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240313220815.20998-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).