From: Chuck Lever <chuck.lever@oracle.com>
To: Henry Shao <hshao@netlogicmicro.com>
Cc: linux-nfs@vger.kernel.org, steved@redhat.com,
Jeff Layton <jlayton@redhat.com>
Subject: Re: About configure error
Date: Tue, 29 Jun 2010 11:22:48 -0400 [thread overview]
Message-ID: <4C2A0FC8.2020607@oracle.com> (raw)
In-Reply-To: <74B0AE1BA53C37449DE49BB274F9A2DB2B3DAA@orion8.netlogicmicro.com>
On 06/28/10 07:32 PM, Henry Shao wrote:
> Hi Chuck:
>
> Thanks for the response.
> Even I do "--disable-tirpc", it give me another error, can't find libwrap
> Can you point to me where can I download libwrap source? I searched google, can't find a linux version.
> Or how can I disable libwrap?
> ...
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for prctl... yes
> checking for cap_get_proc in -lcap... yes
> checking sys/capability.h usability... yes
> checking sys/capability.h presence... no
> configure: WARNING: sys/capability.h: accepted by the compiler, rejected by the preprocessor!
> configure: WARNING: sys/capability.h: proceeding with the compiler's result
> checking for sys/capability.h... yes
> checking for libwrap... configure: error: *** libwrap missing
>
>
> Thanks a million!
libwrap refers to the tcp_wrappers library. It is available in many if
not all Linux distributions. How you get it depends on how your
distribution packages libraries for cross-compilation.
But I think you can disable that using --without-tcp-wrappers.
> -----Original Message-----
> From: Chuck Lever [mailto:chuck.lever@oracle.com]
> Sent: Mon 6/28/2010 7:22 AM
> To: Henry Shao
> Cc: linux-nfs@vger.kernel.org; steved@redhat.com; Jeff Layton
> Subject: Re: About configure error
>
> On 06/26/10 03:37 PM, Henry Shao wrote:
>>
>> Hi Sir:
>>
>> I try to compile nfs-utils-1.2.2 for our mips64 platform using cross compiler. I keek get configure error:
>> checking for clnt_tli_create in -ltirpc... no
>> configure: error: libtirpc not found.
>>
>> Then I download libtirpc and compile it successfully and install it in ../lib directory. I try to use LIBS or exec_prefix ... to pass it in. It did not successful. Still keeping get this error.
>>
>> Do you mind to tell me how can I pass this error and get it compiled for our mips target?
>>
>> Thank you very much!
>>
>>
>>
>> # CC=mipsisa64r2rmi-linux-gcc ./configure --host=mips-linux --disable-gss --disable-nfsv4
>
> ./configure should have noticed that libtirpc was missing and then
> automatically set --disable-tirpc. As a workaround you could manually
> specify --disable-tirpc on your ./configure command line.
>
> After installing libtirpc, though, maybe you need to run ./configure
> again from scratch:
>
> $ make distclean
> $ sh autogen.sh
> $ ./configure ....
>
> If you are trying to install and use a local copy of libtirpc (ie one
> that is not installed in /usr/lib), that may not be supported.
>
prev parent reply other threads:[~2010-06-29 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 19:37 About configure error Henry Shao
[not found] ` <74B0AE1BA53C37449DE49BB274F9A2DB2B3DA2-eoZZxEticU+jYOuY2elzORyIOQ/kevag@public.gmane.org>
2010-06-28 14:22 ` Chuck Lever
2010-06-28 23:32 ` Henry Shao
2010-06-29 15:22 ` Chuck Lever [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=4C2A0FC8.2020607@oracle.com \
--to=chuck.lever@oracle.com \
--cc=hshao@netlogicmicro.com \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--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 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).