From: Paul Bender <pebender@san.rr.com>
To: linux-nfs@vger.kernel.org
Subject: problem with the --enable-libmount-mount configure option
Date: Fri, 29 Jul 2011 21:51:29 -0700 [thread overview]
Message-ID: <4E338DD1.9070704@san.rr.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 195 bytes --]
nfs-utils' configure script assumes that when either
--enable-libmount-mount
or
--disable-libmount-mount
is specified, that libmount should be used. The attached patch fixes the
problem for me.
[-- Attachment #2: nfs-utils-1.2.4-enable_libmount.patch.gz --]
[-- Type: application/gzip, Size: 305 bytes --]
next reply other threads:[~2011-07-30 4:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 4:51 Paul Bender [this message]
2011-08-03 17:43 ` problem with the --enable-libmount-mount configure option Steve Dickson
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=4E338DD1.9070704@san.rr.com \
--to=pebender@san.rr.com \
--cc=linux-nfs@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 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.