From: Tom Tucker <tom-/Yg/VP3ZvrM@public.gmane.org>
To: rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
brandt-4OHPYypu0djtX7QSmKvirg@public.gmane.org,
tom-/Yg/VP3ZvrM@public.gmane.org,
swise-/Yg/VP3ZvrM@public.gmane.org
Subject: [RFC PATCH 1/3] libibverbs: Fix libtool configure warning
Date: Thu, 29 Jul 2010 11:31:51 -0500 [thread overview]
Message-ID: <20100729163151.14901.60182.stgit@build.ogc.int> (raw)
In-Reply-To: <20100729163030.14901.87547.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
From: Tom Tucker <tom-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Added AC_PROG_LIBTOOL to configure.in to fix an autogen.sh warning about
LIBTOOL configuration.
Signed-off-by: Tom Tucker <tom-/Yg/VP3ZvrM@public.gmane.org>
---
configure.in | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure.in b/configure.in
index 927c406..2bb4aee 100644
--- a/configure.in
+++ b/configure.in
@@ -12,6 +12,7 @@ dnl Checks for programs
AC_PROG_CC
AC_GNU_SOURCE
AC_PROG_LN_S
+AC_PROG_LIBTOOL
LT_INIT
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-29 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 16:31 [RFC PATCH 0/3] libibverbs: Add I/O memory registration verbs Tom Tucker
[not found] ` <20100729163030.14901.87547.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-07-29 16:31 ` Tom Tucker [this message]
2010-07-29 16:31 ` [RFC PATCH 2/3] libibverbs: Add reg/unreg I/O memory commands to kern ABI Tom Tucker
2010-07-29 16:32 ` [RFC PATCH 3/3] libibverbs: Add reg/unreg I/O memory verbs Tom Tucker
[not found] ` <20100729163202.14901.44211.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2010-07-29 20:07 ` Ralph Campbell
[not found] ` <1280434056.6820.136.camel-/vjeY7uYZjrPXfVEPVhPGq6RkeBMCJyt@public.gmane.org>
2010-07-29 20:19 ` Jason Gunthorpe
2010-07-29 20:32 ` Tom Tucker
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=20100729163151.14901.60182.stgit@build.ogc.int \
--to=tom-/yg/vp3zvrm@public.gmane.org \
--cc=brandt-4OHPYypu0djtX7QSmKvirg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=swise-/Yg/VP3ZvrM@public.gmane.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.