From: Steve Dickson <SteveD@redhat.com>
To: Anibal Monsalve Salazar <anibal@debian.org>
Cc: Kevin Coffman <kwc@umich.edu>,
linux-nfs@vger.kernel.org, Michael Rasmussen <mir@datanom.net>,
651032@bugs.debian.org, Rares Aioanei <schaiba@gmail.com>,
649491@bugs.debian.org, Bjoern Buerger <bbu@pengutronix.de>,
650904@bugs.debian.org, steven@nchc.org.tw,
650948@bugs.debian.org
Subject: Re: Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library
Date: Mon, 05 Dec 2011 15:20:59 -0500 [thread overview]
Message-ID: <4EDD27AB.9010803@RedHat.com> (raw)
In-Reply-To: <20111205184206.GA5207@debian.org>
On 12/05/2011 01:42 PM, Anibal Monsalve Salazar wrote:
> On Mon, Dec 05, 2011 at 10:52:18AM -0500, Steve Dickson wrote:
>> Why not just use the --with-pluginpath configuration flag?
>> That's how we do it in Fedora...
>
> The --with-pluginpath configuration option isn't in 0.24.
>
> I run
>
> ./configure --help
>
> and it doesn't list the --with-pluginpath configuration option.
>
> The configure commands doesn't unrecognize the --with-pluginpath option.
> See below.
>
> CFLAGS="-Wall -g -O2" ./configure --host=i486-linux-gnu \
> --build=i486-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info --with-pluginpath=/lib/libnfsidmap
> configure: WARNING: unrecognized options: --with-pluginpath
>
> The git repo has patches to add the --with-pluginpath configuration
> option. Do you plan to release libnfsidmap 0.25 soon?
Sure.. I'll try to get one out asap...
steved.
next prev parent reply other threads:[~2011-12-05 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111205071808.5626.67399.reportbug@sleipner.datanom.net>
2011-12-05 8:25 ` Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library Anibal Monsalve Salazar
2011-12-05 15:52 ` Steve Dickson
2011-12-05 18:42 ` Anibal Monsalve Salazar
2011-12-05 20:20 ` Steve Dickson [this message]
2011-12-07 12:44 ` Steven Shiau
2011-12-07 14:35 ` Rares Aioanei
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=4EDD27AB.9010803@RedHat.com \
--to=steved@redhat.com \
--cc=649491@bugs.debian.org \
--cc=650904@bugs.debian.org \
--cc=650948@bugs.debian.org \
--cc=651032@bugs.debian.org \
--cc=anibal@debian.org \
--cc=bbu@pengutronix.de \
--cc=kwc@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=mir@datanom.net \
--cc=schaiba@gmail.com \
--cc=steven@nchc.org.tw \
/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.