From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: rpcbind doesn't build on Fedora 12 ?
Date: Tue, 05 Jan 2010 14:22:30 -0500 [thread overview]
Message-ID: <4B439176.5080702@RedHat.com> (raw)
In-Reply-To: <158159AE-BD50-4D41-9B14-450241B42E23@oracle.com>
On 01/05/2010 01:58 PM, Chuck Lever wrote:
> On Jan 5, 2010, at 1:44 PM, Steve Dickson wrote:
>> On 01/05/2010 12:12 PM, Chuck Lever wrote:
>>> security.c:24:27: error: rpcsvc/rquota.h: No such file or directory
>>> security.c: In function =91check_callit=92:
>>> security.c:286: error: =91RQUOTAPROG=92 undeclared (first use in th=
is
>>> function)
>>> security.c:286: error: (Each undeclared identifier is reported only=
once
>>> security.c:286: error: for each function it appears in.)
>>>
>>> I have libtirpc-devel installed, but a "find" on /usr/include turns=
up
>>> no file named rquota.h. Am I missing some other package?
>>>
>> Yeah... 'yum install quota-devel' is your friend...
>=20
> That fixes it, but... I never had to install this package before.=20
> Either it's new with Fedora 12, or the Fedora 12 install with "softwa=
re
> development" checked doesn't install this one any more.
Packages do come and go with different Fedora releases...=20
>=20
> Is there a good reason why an RPC header would be separated into a
> non-obvious package like this?
>=20
Not that I know of...
steved.
prev parent reply other threads:[~2010-01-05 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 17:12 rpcbind doesn't build on Fedora 12 ? Chuck Lever
2010-01-05 18:44 ` Steve Dickson
[not found] ` <4B43887D.2000006-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-01-05 18:58 ` Chuck Lever
2010-01-05 19:22 ` Steve Dickson [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=4B439176.5080702@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.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.