From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 1/3] configure: Remove inet_ntop(3) check from configure.ac
Date: Tue, 06 Jan 2009 18:22:44 -0500 [thread overview]
Message-ID: <20090106232244.24661.66031.stgit@ingres.1015granger.net> (raw)
In-Reply-To: <20090106231909.24661.92964.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
nfs-utils no longer uses inet_ntop(3) so remove checks for it from
configure.ac.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
configure.ac | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/configure.ac b/configure.ac
index 7140f48..4448743 100644
--- a/configure.ac
+++ b/configure.ac
@@ -252,8 +252,6 @@ AC_CHECK_DECL([AI_ADDRCONFIG],
[ #include <netdb.h> ] )
if test "$enable_ipv6" = yes; then
- AC_CHECK_FUNC(inet_ntop, , ,
- AC_MSG_ERROR(Function 'inet_ntop' not found.))
AC_CHECK_FUNC(getnameinfo, , ,
AC_MSG_ERROR(Function 'getnameinfo' not found.))
AC_CHECK_LIB(tirpc, clnt_tli_create, ,
@@ -309,7 +307,7 @@ AC_FUNC_STAT
AC_FUNC_VPRINTF
AC_CHECK_FUNCS([alarm atexit dup2 fdatasync ftruncate getcwd \
gethostbyaddr gethostbyname gethostname getmntent \
- inet_ntop getnameinfo getrpcbyname \
+ getnameinfo getrpcbyname \
bindresvport_sa getnetconfig \
clnt_create clnt_create_timed \
clnt_tli_create clnt_vc_create clnt_dg_create xdr_rpcb \
next prev parent reply other threads:[~2009-01-06 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 23:22 [PATCH 0/3] Three more nfs-utils clean ups Chuck Lever
[not found] ` <20090106231909.24661.92964.stgit-07a7zB5ZJzbwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2009-01-06 23:22 ` Chuck Lever [this message]
2009-01-06 23:22 ` [PATCH 2/3] configure: Add new build option "--enable-tirpc" Chuck Lever
2009-01-06 23:22 ` [PATCH 3/3] showmount command: Quiesce warning when TI-RPC is disabled Chuck Lever
2009-01-07 17:54 ` [PATCH 0/3] Three more nfs-utils clean ups 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=20090106232244.24661.66031.stgit@ingres.1015granger.net \
--to=chuck.lever@oracle.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