linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yongcheng Yang <yongcheng.yang@gmail.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs-utils: nfsidmap fail to build if no --with-pluginpath specified
Date: Wed, 17 Apr 2019 17:22:47 +0800	[thread overview]
Message-ID: <20190417092246.GA5865@yoyang-pc.usersys.redhat.com> (raw)
In-Reply-To: <95e49187-6d99-4168-1bb1-4a3f6f2500ee@RedHat.com>

Hi SteveD,

On Tue, Apr 16, 2019 at 10:34:51AM -0400, Steve Dickson wrote:
> The only way I see a failure is when ./configure --with-pluginpath= 
> without a path which is wrong... 
> 
> ./configure --with-pluginpath=/usr/lib/libnfsidmap seems to work
> just fine
> 
> I thinking it is better to error out when a path is not given
> then to gloss over but used a default.
> 
> steved.
> 

From what you comments, there should be a plugin path assigned by
default if the user is not aware of it, correct?

Surely "./configure --with-pluginpath=/usr/lib/libnfsidmap" can work.
But I didn't know the specific exact path before.

I was just using "./configure" without any options and find out that
it's empty. (Please find my previous full logs)

Agree with you we should "use a default" one when path is not given.

Thanks,
Yongcheng

  reply	other threads:[~2019-04-17  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  9:16 [PATCH] nfs-utils: nfsidmap fail to build if no --with-pluginpath specified Yongcheng Yang
2019-04-02  9:26 ` Yongcheng Yang
2019-04-16 14:34 ` Steve Dickson
2019-04-17  9:22   ` Yongcheng Yang [this message]
2019-05-10 18:49     ` 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=20190417092246.GA5865@yoyang-pc.usersys.redhat.com \
    --to=yongcheng.yang@gmail.com \
    --cc=SteveD@redhat.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 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).