From: Glenn Washburn <development@efficientek.com>
To: DM-DEVEL ML <dm-devel@lists.linux.dev>
Cc: Glenn Washburn <development@efficientek.com>,
Martin Wilck <mwilck@suse.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>
Subject: [PATCH] README.md: Add libmount to list of build prerequisites
Date: Thu, 4 Apr 2024 19:14:46 -0500 [thread overview]
Message-ID: <20240405001446.442390-1-development@efficientek.com> (raw)
On Debian based systems the libmount development package (ie. libmount-dev)
is required to build. Add it to the list in the README.md.
Signed-off-by: Glenn Washburn <development@efficientek.com>
---
README.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
index d4f35f57c61f..898ea56e9bbd 100644
--- a/README.md
+++ b/README.md
@@ -45,10 +45,10 @@ Select a release-tag and then click on "zip" or "tar.gz".
Building multipath-tools
========================
-Prerequisites: development packages of for `libdevmapper`, `libaio`, `libudev`,
-`libjson-c`, `liburcu`, and `libsystemd`. If commandline editing is enabled
-(see below), the development package for either `libedit` or `libreadline` is
-required as well.
+Prerequisites: development packages of for `libdevmapper`, `libmount`, `libaio`,
+`libudev`, `libjson-c`, `liburcu`, and `libsystemd`. If commandline editing is
+enabled (see below), the development package for either `libedit` or
+`libreadline` is required as well.
Then, build and install multipath-tools with:
--
2.34.1
next reply other threads:[~2024-04-05 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 0:14 Glenn Washburn [this message]
2024-04-05 16:39 ` [PATCH] README.md: Add libmount to list of build prerequisites Martin Wilck
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=20240405001446.442390-1-development@efficientek.com \
--to=development@efficientek.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.