From c0ef28186ee1210ff7849f5139bd38babcda6a41 Mon Sep 17 00:00:00 2001 From: Steve Beattie Date: Fri, 6 Sep 2013 13:45:15 -0700 Subject: [PATCH] Subject: libapparmor - enhance readability of binding checking message This patch makes the binding check messages a little more understandable and coherent. The original messages looked like (for a perl binding only build): checking Checking for Python... no checking Checking for perl... yes checking for perl... /usr/bin/perl Note the duplicated 'checking Checking' and '[cC]hecking for perl' statements. With the patch applied, the output looks like thus: checking whether python bindings are enabled... no checking whether perl bindings are enabled... yes checking for perl... /usr/bin/perl Signed-off-by: Steve Beattie Acked-by: Tyler Hicks --- libraries/libapparmor/configure.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/libraries/libapparmor/configure.in b/libraries/libapparmor/configure.in index 9ab09182e..549f08b2b 100644 --- a/libraries/libapparmor/configure.in +++ b/libraries/libapparmor/configure.in @@ -17,7 +17,7 @@ AC_PATH_PROG([SWIG], [swig]) sinclude(m4/ac_pod2man.m4) PROG_POD2MAN -AC_MSG_CHECKING(Checking for Python) +AC_MSG_CHECKING([whether python bindings are enabled]) AC_ARG_WITH(python, [ --with-python enable the python wrapper [[default=no]]], [AC_MSG_RESULT($withval)], [AC_MSG_RESULT(no)]) @@ -30,7 +30,7 @@ if test "$with_python" = "yes"; then AM_PATH_PYTHON fi -AC_MSG_CHECKING(Checking for perl) +AC_MSG_CHECKING([whether perl bindings are enabled]) AC_ARG_WITH(perl, [ --with-perl enable the perl wrapper [[default=no]]], [AC_MSG_RESULT($withval)], [AC_MSG_RESULT(no)]) @@ -43,7 +43,7 @@ if test "$with_perl" = "yes"; then fi -AC_MSG_CHECKING(Checking for ruby) +AC_MSG_CHECKING([whether ruby bindings are enabled]) AC_ARG_WITH(ruby, [ --with-ruby enable the ruby wrapper [[default=no]]], [AC_MSG_RESULT($withval)], [AC_MSG_RESULT(no)])