check.mak: fail valgrind checks only if we find == at the beginning of a line

Otherwise valgrind checks will fail if there's a "==" anywhere in the
output, which can easily happen when running with debug logging
enabled, for example.

1 files changed, 1 insertions, 1 deletions

diff --git a/check.mak b/check.mak
index 8a90b5d..25a16e6 100644
--- a/check.mak
+++ b/check.mak
@@ -57,7 +57,7 @@ LOOPS ?= 10
 	--show-possibly-lost=no                                 \
 	--leak-resolution=high --num-callers=20			\
 	./$* 2>&1 | tee $$valgrind_log ;			\
-	if grep "==" $$valgrind_log > /dev/null 2>&1; then	\
+	if grep "^==" $$valgrind_log > /dev/null 2>&1; then	\
 	    rm $$valgrind_log;					\
 	    exit 1;						\
 	fi ;							\