From: Chuck Lever <chuck.lever@oracle.com>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: NFSv3 list <linux-nfs@vger.kernel.org>,
nfsv4@linux-nfs.org, Jeff Layton <jlayton@redhat.com>
Subject: Re: ANNOUNCE: nfs-utils-1.2.2 released.
Date: Thu, 04 Mar 2010 17:30:29 -0500 [thread overview]
Message-ID: <4B903485.1030608@oracle.com> (raw)
In-Reply-To: <20100304212149.GM19154@ics.muni.cz>
On 03/04/2010 04:21 PM, Lukas Hejtmanek wrote:
> On Thu, Mar 04, 2010 at 04:11:11PM -0500, Chuck Lever wrote:
>> You may be missing some other package, like libgssglue-devel. Or
>> there could be a bug. But, nfs-utils should compile and work using
>> --disable-tirpc.
>>
>> What does your configure.ac command line look like?
>
> without --disable-tirpc it looks like this:
> anubis: /tmp/nfs-utils-1.2.2 $ ./configure
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for clnt_tli_create in -ltirpc... no
> configure: error: libtirpc not found.
That's a bug. The configure script is supposed to disable TI-RPC
automatically if it can't find libtirpc.
> So I did a try with --disable-tirpc
> configure runs fine.
> Looks like it finds proper libs:
> checking for gss_krb5_export_lucid_sec_context in -lgssapi_krb5... yes
> checking for gss_krb5_set_allowable_enctypes in -lgssapi_krb5... yes
> checking for gss_krb5_ccache_name in -lgssapi_krb5... yes
> checking for krb5_get_error_message in -lgssapi_krb5... yes
> checking for krb5_get_init_creds_opt_set_addressless in -lgssapi_krb5... no
> checking for authgss_create_default in -lrpcsecgss... yes
> checking for authgss_set_debug_level in -lrpcsecgss... yes
>
> I do have libgssglue-dev.
>
> make finishes like this:
> gcc -DHAVE_CONFIG_H -I. -I../../support/include -D_GNU_SOURCE -Wall
> -Wstrict-prototypes -pipe -g -O2 -g -O2 -MT gssd-context.o -MD -MP -MF
> .deps/gssd-context.Tpo -c -o gssd-context.o `test -f 'context.c' || echo
> './'`context.c
> context.c:40:26: error: rpc/auth_gss.h: No such file or directory
> make[2]: *** [gssd-context.o] Error 1
> make[2]: Leaving directory `/tmp/nfs-utils-1.2.2/utils/gssd'
>
> dpkg -S rpc/auth_gss.h
> librpcsecgss-dev: /usr/include/rpcsecgss/rpc/auth_gss.h
Likely configure isn't setting up the include path correctly.
> the configure.ac is the one from nfs-utils-1.2.2 tar ball. It is not
> autogenerated, right?
F12 (which I'm using) appears to have 3 copies of auth_gss.h; one in
/usr/include/gssrpc, one in /usr/include/rpcsecgss, and one in
/usr/include/tirpc.
I'm not sure, but I think you will have to go through the full motions
of setting up configure on your system so it can find everything it needs.
I use
$ make distclean
$ sh ./autogen.sh
then run ./configure
--
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2010-03-04 22:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 14:27 ANNOUNCE: nfs-utils-1.2.2 released Steve Dickson
[not found] ` <20100304201941.GL19154@ics.muni.cz>
[not found] ` <4B9021EF.60309@oracle.com>
[not found] ` <20100304212149.GM19154@ics.muni.cz>
2010-03-04 22:30 ` Chuck Lever [this message]
2010-03-04 22:40 ` Lukas Hejtmanek
2010-03-08 10:16 ` Lukas Hejtmanek
2010-03-08 12:02 ` Jeff Layton
2010-03-08 12:11 ` Lukas Hejtmanek
2010-03-08 13:44 ` Kevin Coffman
2010-03-08 15:30 ` Lukas Hejtmanek
2010-03-08 19:21 ` Kevin Coffman
2010-03-08 19:40 ` Lukas Hejtmanek
2010-03-08 19:48 ` Jeff Layton
[not found] ` <20100308144825.0e1afa59-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-03-09 10:35 ` Lukas Hejtmanek
2010-03-09 15:18 ` Kevin Coffman
2010-03-09 15:53 ` Lukas Hejtmanek
2010-03-09 17:04 ` Kevin Coffman
2010-03-09 17:29 ` Lukas Hejtmanek
2010-03-09 17:41 ` Lukas Hejtmanek
2010-03-09 18:26 ` Kevin Coffman
2010-03-09 18:52 ` Lukas Hejtmanek
2010-03-08 19:48 ` Kevin Coffman
2010-03-08 17:42 ` 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=4B903485.1030608@oracle.com \
--to=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=xhejtman@ics.muni.cz \
/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