All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Farrellee <matt@redhat.com>
To: hail-devel@vger.kernel.org
Subject: [PATCH] chunkd: Make AC_CHECK_LIB failure for libevent explicit
Date: Wed, 29 Jul 2009 13:58:03 -0500	[thread overview]
Message-ID: <4A709BBB.1090005@redhat.com> (raw)

When libevent headers were missing, configure would complete with an
exit code of 1, but no clear message as to what failed. This patch
makes things more clear as to why configure is exiting. It could be
extended to include information about needing libevent headers or
development libraries.

Signed-off-by: Matthew Farrellee <matt@redhat.com>
---
 configure.ac |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/configure.ac b/configure.ac
index acea808..7e51b84 100644
--- a/configure.ac
+++ b/configure.ac
@@ -74,7 +74,8 @@ dnl Checks for required libraries
 dnl -----------------------------
 AC_CHECK_LIB(crypto, MD5_Init, CRYPTO_LIBS=-lcrypto)
 AC_CHECK_LIB(ssl, SSL_new, SSL_LIBS=-lssl)
-AC_CHECK_LIB(event, event_base_new, EVENT_LIBS=-levent, exit 1)
+AC_CHECK_LIB(event, event_base_new, EVENT_LIBS=-levent,
+   [AC_MSG_ERROR([Missing required libevent])])
 AC_CHECK_LIB(argp, argp_parse, ARGP_LIBS=-largp)
 AC_CHECK_LIB(socket, bind, SOCKET_LIBS=-lsocket)
 PKG_CHECK_MODULES(CLDC, libcldc)
-- 
1.6.0.6


             reply	other threads:[~2009-07-29 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 18:58 Matthew Farrellee [this message]
2009-07-29 19:05 ` [PATCH] chunkd: Make AC_CHECK_LIB failure for libevent explicit Jeff Garzik
2009-07-30  1:36 ` Jeff Garzik
2009-07-30 14:30   ` [PATCH] configure.ac reports errors instead of exiting quietly Matthew Farrellee
2009-07-30 20:42     ` Jeff Garzik
2009-07-30 21:32       ` Matthew Farrellee
2009-08-01  4:37     ` Jeff Garzik

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=4A709BBB.1090005@redhat.com \
    --to=matt@redhat.com \
    --cc=hail-devel@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.