From: Steve Dickson <SteveD@redhat.com>
To: lux-integ <lux-integ@btconnect.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs-utils, --enable-gss librpcsecgss.so glitch
Date: Fri, 26 Oct 2012 06:56:06 -0400 [thread overview]
Message-ID: <508A6C46.2070309@RedHat.com> (raw)
In-Reply-To: <201210260234.04247.lux-integ@btconnect.com>
On 25/10/12 21:34, lux-integ wrote:
> Greetings,
>
> I hope I am posting to the right list.
>
> I am trying to compile nfs-utils on a cblfs setup with (
> gcc-4.6.3,
> linx-3.6.3,
> kerberos-10.3
> as well as
> librpcsecgss-0.19 and
> libgssglue-0.4 )
>
>
> I tried nfs-utils 1.2.5, 1.2.6. and r.1.2.7rc7 In all instances
>
> with the --disable-gss , compilation sicceeds
> BUT
> with --enable-gss (the default)
> make ends like so.
> #########
> /usr/lib/librpcsecgss.so: undefined reference to `__rpc_thread_svc_fdset'
> collect2: ld returned 1 exit status
> make[2]: *** [gssd] Error 1
> ########
This was define in glibc... I wonder if its deprecated
steved.
>
> The thing is, I want the gss feature for an NFSv4 setup.
>
> I have successfully compiled earlier versions of nfs-utils on hosts with
> earlier versions of kerberos, librpcsecgss-and libgssglue
>
> I would be grateful for advice concerning the current setup and result(s)
>
> sincerely
> lux-integ
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-10-26 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 1:34 nfs-utils, --enable-gss librpcsecgss.so glitch lux-integ
2012-10-26 10:56 ` Steve Dickson [this message]
2012-10-26 17:01 ` lux-integ
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=508A6C46.2070309@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lux-integ@btconnect.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 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).