From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.com>, <dev@dpdk.org>
Subject: RE: [PATCH] doc/linux_gsg: update recommended compiler versions
Date: Wed, 9 Apr 2025 07:50:30 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9FBA5@smartserver.smartshare.dk> (raw)
In-Reply-To: <20250408171835.2833766-1-bruce.richardson@intel.com>
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
> Sent: Tuesday, 8 April 2025 19.19
>
> 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
Acked-by: Morten Brørup <mb@smartsharesystems.com>
prev parent reply other threads:[~2025-04-09 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 17:18 Bruce Richardson
2025-04-09 5:50 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35E9FBA5@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=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).