Commit 25e40760 authored by conrad's avatar conrad

remove the need to run under --disable-shared to run tests under valgrind,

by using 'libtool --mode=execute valgrind ...".
Thanks to thomasvs for the tip :-)


git-svn-id: http://svn.annodex.net/liboggz/trunk@1348 8158c8cd-e7e1-0310-9fa4-c5954c97daef
parent 0660a6d8
......@@ -55,6 +55,7 @@ AC_CHECK_PROG(HAVE_DOCBOOK2HTML, docbook2html, true, false)
AM_CONDITIONAL(HAVE_DOCBOOK2HTML,$HAVE_DOCBOOK2HTML)
# Check for valgrind
VALGRIND_ENVIRONMENT=""
ac_enable_valgrind=no
AC_ARG_ENABLE(valgrind-testing,
[ --enable-valgrind-testing enable running of tests inside Valgrind ],
......@@ -62,16 +63,12 @@ AC_ARG_ENABLE(valgrind-testing,
if test "x${ac_enable_valgrind}" = xyes ; then
if test "x${enable_shared}" = xyes ; then
AC_MSG_WARN([
*** You have requested to test under valgrind, but have not disabled the
*** building of shared libraries. You usually need to do:
*** ./configure --disable-shared --enable-valgrind-testing
*** for Valgrind to produce useful output.])
VALGRIND_ENVIRONMENT="libtool --mode=execute "
fi
AC_CHECK_PROG(HAVE_VALGRIND, valgrind, yes, no)
if test "x$HAVE_VALGRIND" = xyes ; then
VALGRIND_ENVIRONMENT="valgrind -q --leak-check=yes --show-reachable=yes --num-callers=100"
VALGRIND_ENVIRONMENT="$VALGRIND_ENVIRONMENT valgrind -q --leak-check=yes --show-reachable=yes --num-callers=100"
AC_SUBST(VALGRIND_ENVIRONMENT)
TESTS_INFO="Test suite will be run under:
${VALGRIND_ENVIRONMENT}"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment