From: David Disseldorp <ddiss@suse.de>
To: linux-doc@vger.kernel.org
Cc: David Disseldorp <ddiss@suse.de>
Subject: [PATCH] docs: fix openSUSE libelf-devel package name
Date: Fri, 26 Jun 2026 14:48:04 +1000 [thread overview]
Message-ID: <20260626044804.14258-1-ddiss@suse.de> (raw)
The proposed "zypper install ... libelf-dev" invocation results in an
error:
'libelf-dev' not found in package names. Trying capabilities.
No provider of 'libelf-dev' found.
openSUSE and derivitives (Tumbleweed, Leap and SLES) use a "devel"
suffix instead of "dev".
Link: https://build.opensuse.org/projects/openSUSE:Factory/packages/elfutils/files/elfutils.spec
Signed-off-by: David Disseldorp <ddiss@suse.de>
---
Documentation/admin-guide/quickly-build-trimmed-linux.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/quickly-build-trimmed-linux.rst b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
index cb178e0a62084..f6b31d7207ff6 100644
--- a/Documentation/admin-guide/quickly-build-trimmed-linux.rst
+++ b/Documentation/admin-guide/quickly-build-trimmed-linux.rst
@@ -446,7 +446,7 @@ distributions:
* openSUSE and derivatives::
sudo zypper install bc binutils bison dwarves flex gcc git make perl-base \
- openssl openssl-devel libelf-dev
+ openssl openssl-devel libelf-devel
In case you wonder why these lists include openssl and its development headers:
they are needed for the Secure Boot support, which many distributions enable in
--
2.54.0
next reply other threads:[~2026-06-26 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 4:48 David Disseldorp [this message]
2026-06-26 19:50 ` [PATCH] docs: fix openSUSE libelf-devel package name Randy Dunlap
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=20260626044804.14258-1-ddiss@suse.de \
--to=ddiss@suse.de \
--cc=linux-doc@vger.kernel.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