From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] doc/linux_gsg: update recommended compiler versions
Date: Tue, 8 Apr 2025 18:18:35 +0100 [thread overview]
Message-ID: <20250408171835.2833766-1-bruce.richardson@intel.com> (raw)
Rather than specifying a minimum compiler version, update the docs to
recommend a particular compiler version. In other words, earlier
versions may work, but are not officially supported, or may give reduced
functionality.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
doc/guides/linux_gsg/sys_reqs.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst
index 4c9d0c55c0..0acd26f260 100644
--- a/doc/guides/linux_gsg/sys_reqs.rst
+++ b/doc/guides/linux_gsg/sys_reqs.rst
@@ -28,7 +28,8 @@ Compilation of the DPDK
For details on Linux distributions and the versions tested, please consult the DPDK Release Notes.
* General development tools including a C compiler supporting the C11 standard,
- including standard atomics, for example: GCC (version 5.0+) or Clang (version 3.6+),
+ including standard atomics, for example:
+ GCC (version 8.0+ recommended) or Clang (version 7+ recommended),
and ``pkg-config`` or ``pkgconf`` to be used when building end-user binaries against DPDK.
* For RHEL/Fedora systems these can be installed using ``dnf groupinstall "Development Tools"``
--
2.45.2
next reply other threads:[~2025-04-08 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 17:18 Bruce Richardson [this message]
2025-04-09 5:50 ` Morten Brørup
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=20250408171835.2833766-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--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).