[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Valgrind check: No rule to make target 'check-TESTS'

From: Philip Withnall
Subject: Re: Valgrind check: No rule to make target 'check-TESTS'
Date: Mon, 01 Aug 2016 15:02:05 +0100

On Mon, 2016-08-01 at 15:26 +0200, Sébastien Wilmet wrote:
> Hello,
> I would like to use ax_valgrind_check.m4, but I have the following
> error:
> $ make check-valgrind-memcheck 
> make check-TESTS \
>         TESTS_ENVIRONMENT=" env VALGRIND=valgrind G_SLICE=always-
> malloc,debug-blocks G_DEBUG=fatal-warnings,fatal-criticals,gc-
> friendly" \
>         LOG_COMPILER="/bin/sh ./libtool   --mode=execute valgrind  
> --error-exitcode=1 --num-callers=30" \
>         LOG_FLAGS="--tool=memcheck --leak-check=full --show-
> reachable=no" \
>         TEST_SUITE_LOG=test-suite-memcheck.log
> make[1]: Entering directory '/home/seb/gnome/gspell'
> make[1]: *** No rule to make target 'check-TESTS'.  Stop.
> make[1]: Leaving directory '/home/seb/gnome/gspell'
> Makefile:1220: recipe for target 'check-valgrind-memcheck' failed
> make: *** [check-valgrind-memcheck] Error 2
> There is no check-TESTS target in the project that I maintain, here
> gspell. See its testsuite/
> 2
> It's basically using:
> So, is this a bug in ax_valgrind_check.m4? Or does it make some
> assumptions that are not applied in gspell?

I suspect you have added @VALGRIND_CHECK_RULES@ to
$top_srcdir/, and are running `make check-valgrind-memcheck` 
there. What you need to do instead is to add @VALGRIND_CHECK_RULES@ to
$top_srcdir/testsuite/, and run `make -C testsuite check-

check-TESTS should be defined in $top_builddir/testsuite/,
but not in $top_builddir/, since you don’t have any tests
defined there.


Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]