From: Simo Sorce <simo@redhat.com>
To: Jim Rees <rees@umich.edu>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"libtirpc-devel@lists.sourceforge.net"
<libtirpc-devel@lists.sourceforge.net>,
linux-nfs <linux-nfs@vger.kernel.org>,
Steve Dickson <steved@redhat.com>
Subject: Re: Allow building libtirpc directly against GSSAPI
Date: Tue, 26 Mar 2013 12:56:52 -0400 [thread overview]
Message-ID: <1364317012.2660.129.camel@willson.li.ssimo.org> (raw)
In-Reply-To: <20130326155645.GA31975@umich.edu>
On Tue, 2013-03-26 at 11:56 -0400, Jim Rees wrote:
> Doesn't nfs-utils build without gssglue if libgssglue is not installed?
Not really, both libtirpc needs --enable-gss, if yo pass that they check
only for libgssglue right now and fail if not available.
> If that's true I see no reason to change the default. If you don't want
> gssglue, uninstall it. If you have it installed and want to build without
> it, use --without-gssglue.
I am changing the default to build against system GSSAPI libraries when
--enable-gss is passed in, if you want to force to build against
libgssglue for some specific reason you use --with-gssglue
I believe building against system libraries instead of a shim is the
better default in the general case.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
next prev parent reply other threads:[~2013-03-26 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:41 Allow building libtirpc directly against GSSAPI Simo Sorce
2013-03-26 15:22 ` Steve Dickson
2013-03-26 15:25 ` Myklebust, Trond
2013-03-26 15:37 ` Simo Sorce
2013-03-26 15:43 ` Myklebust, Trond
2013-03-26 15:49 ` Simo Sorce
2013-03-26 15:56 ` Jim Rees
2013-03-26 16:56 ` Simo Sorce [this message]
2013-03-27 1:14 ` Alex Dubov
2013-04-02 18:02 ` 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=1364317012.2660.129.camel@willson.li.ssimo.org \
--to=simo@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=steved@redhat.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.