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.

Changelog:
  - removed --disable-debug option of configure script, removing debug
    messages we would save 'amazing' 4kB, which is IMO not worth it.

Signed-off-by: Peter Schiffer <pschi...@redhat.com>
---
 configure.in             |   11 -----------
 src/libcgroup-internal.h |    5 -----
 2 files changed, 16 deletions(-)

diff --git a/configure.in b/configure.in
index 29be7a4..8284c1b 100644
--- a/configure.in
+++ b/configure.in
@@ -45,17 +45,6 @@ AC_ARG_ENABLE([bindings],
 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_ARG_ENABLE([tools],
        [AC_HELP_STRING([--enable-tools],
                [compile libcgroup tools [default=yes]])],
diff --git a/src/libcgroup-internal.h b/src/libcgroup-internal.h
index 47ee2ab..4c0f46c 100644
--- a/src/libcgroup-internal.h
+++ b/src/libcgroup-internal.h
@@ -64,12 +64,7 @@ __BEGIN_DECLS
 #define cgroup_err(x...) cgroup_log(CGROUP_LOG_ERROR, x)
 #define cgroup_warn(x...) cgroup_log(CGROUP_LOG_WARNING, x)
 #define cgroup_info(x...) cgroup_log(CGROUP_LOG_INFO, x)
-
-#ifdef CGROUP_DEBUG
 #define cgroup_dbg(x...) cgroup_log(CGROUP_LOG_DEBUG, x)
-#else
-#define cgroup_dbg(x...) do {} while (0)
-#endif
 
 #define CGROUP_DEFAULT_LOGLEVEL CGROUP_LOG_ERROR
 


------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Libcg-devel mailing list
Libcg-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libcg-devel

Reply via email to