From: "lux-integ" <lux-integ@btconnect.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs-utils, --enable-gss librpcsecgss.so glitch
Date: Fri, 26 Oct 2012 18:01:06 +0100 [thread overview]
Message-ID: <201210261801.06308.lux-integ@btconnect.com> (raw)
In-Reply-To: <508A6C46.2070309@RedHat.com>
On Friday 26 October 2012 11:56:06 Steve Dickson wrote:
> > 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.
>
I forgot to mention that my setup has glibc-2.15.
So the problem maybe the installation of libtirpc which uses depreciated
headers ( post glibc-2.15 ).
I followed this recipe:-
http://www.linuxfromscratch.org/blfs/view/svn/basicnet/libtirpc.html
SO
Do you
(or enyone else on list )
know of a recipe to compile/install libtirpc-0.2.2 on a setup with
glibc-2.15/gcc-4.6.3/linux-3.6.3 ?
Alternatively do you know of an available nfs-1.2.6(+)-useable version of
libtirpc that compiles/installs on a setup with
glibc-2.15/gcc-4.6.3/linux-3.6.3 ?
thanks in advance
sincerely
lux-integ
prev parent reply other threads:[~2012-10-26 16:05 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
2012-10-26 17:01 ` lux-integ [this message]
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=201210261801.06308.lux-integ@btconnect.com \
--to=lux-integ@btconnect.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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.