I've noticed that the debugging info is compiled in even if --disable-debug
is provided. Following patch adds explicit check that --enable-debug or
--enable-debug=yes is provided to configure script.
Signed-off-by: Jan Safranek <jsafr...@redhat.com>
---
configure.in | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/configure.in b/configure.in
index bea714a..b8c8b5f 100644
--- a/configure.in
+++ b/configure.in
@@ -48,8 +48,12 @@ AM_CONDITIONAL([WITH_BINDINGS], [test x$with_bindings =
xtrue])
AC_ARG_ENABLE([debug],
[AC_HELP_STRING([--enable-debug],
[enable extra debugging output [default=no]])],
- [AC_DEFINE([CGROUP_DEBUG], [],
- [Define to enable extra debugging output.])],
+ [
+ if test "x$enableval" = xyes; then
+ AC_DEFINE([CGROUP_DEBUG], [],
+ [Define to enable extra debugging output.])
+ fi
+ ]
[])
AC_ARG_ENABLE([tools],
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
Libcg-devel mailing list
Libcg-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libcg-devel
