From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC] doc: change recommendation for installation of tools on Fedora
Date: Sun, 8 Jun 2025 20:03:05 -0700 [thread overview]
Message-ID: <20250609030306.17171-1-stephen@networkplumber.org> (raw)
The syntax changed with Fedora 41 and the old command is now:
$ sudo dnf group install development-tools
Not sure what is on RHEL 9 or later.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
doc/guides/howto/af_xdp_dp.rst | 2 +-
doc/guides/linux_gsg/sys_reqs.rst | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/howto/af_xdp_dp.rst b/doc/guides/howto/af_xdp_dp.rst
index 9da68e0bfa..b3681af2f7 100644
--- a/doc/guides/howto/af_xdp_dp.rst
+++ b/doc/guides/howto/af_xdp_dp.rst
@@ -159,7 +159,7 @@ Build a DPDK container image (using Docker)
python3-pyelftools \
python38 \
iproute
- RUN dnf groupinstall -y 'Development Tools'
+ RUN dnf group install -y development-tools
# Create DPDK dir and copy over sources
# Create DPDK dir and copy over sources
diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst
index 4c9d0c55c0..c53e79f7d5 100644
--- a/doc/guides/linux_gsg/sys_reqs.rst
+++ b/doc/guides/linux_gsg/sys_reqs.rst
@@ -31,7 +31,7 @@ Compilation of the DPDK
including standard atomics, for example: GCC (version 5.0+) or Clang (version 3.6+),
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"``
+ * For RHEL/Fedora systems these can be installed using ``dnf group install development-tools``
* For Ubuntu/Debian systems these can be installed using ``apt install build-essential``
* For Alpine Linux, ``apk add alpine-sdk bsd-compat-headers``
--
2.47.2
next reply other threads:[~2025-06-09 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 3:03 Stephen Hemminger [this message]
2025-06-09 9:23 ` Varghese, Vipin
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=20250609030306.17171-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).