Debug log messages are now automatically compiled in libcgroup unless
explicitly disabled with ./configure --disable-debug.
Please note that the messages still must be enabled in runtime by setting
appropriate log level, e.g. export CGROUP_LOGLEVEL=DEBUG.
Signed-off-by: Jan Safranek <jsafr...@redhat.com>
---
configure.in | 17 ++++++++---------
1 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/configure.in b/configure.in
index d1f19a2..604b9fa 100644
--- a/configure.in
+++ b/configure.in
@@ -46,15 +46,14 @@ AM_CONDITIONAL([WITH_BINDINGS], [test x$with_bindings =
xtrue])
# Process command line options
AC_ARG_ENABLE([debug],
- [AC_HELP_STRING([--enable-debug],
- [enable extra debugging output [default=no]])],
- [
- if test "x$enableval" = xyes; then
- AC_DEFINE([CGROUP_DEBUG], [],
- [Define to enable extra debugging output.])
- fi
- ]
- [])
+ [AC_HELP_STRING([--disable-debug],
+ [Do not compile debugging log messages to reduce resulting size
+ of libcgroup binaries.])])
+
+AS_IF([test "x$enable_debug" != "xno"], [
+ AC_DEFINE([CGROUP_DEBUG], [],
+ [Define to compile in extra debugging log messages.])
+])
AC_ARG_ENABLE([tools],
[AC_HELP_STRING([--enable-tools],
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Libcg-devel mailing list
Libcg-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libcg-devel
