Date:   Wed, 17 Apr 2019 17:22:47 +0800
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
Message-ID: <20190417092246.GA5865@yoyang-pc.usersys.redhat.com>
References: <20190402091651.17186-1-yongcheng.yang@gmail.com>
 <95e49187-6d99-4168-1bb1-4a3f6f2500ee@RedHat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <95e49187-6d99-4168-1bb1-4a3f6f2500ee@RedHat.com>
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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