From 6380d4b370f078f0cca7240428ea9f6639571ff5 Mon Sep 17 00:00:00 2001 From: Jan Schmidt Date: Mon, 12 Oct 2009 14:37:15 +0100 Subject: [PATCH] check: Use the LIBTOOL env var rather than hard-coding Instead of hard-coding libtool, use the LIBTOOL env var supplied by the makefiles for the gdb/valgrind targets to ensure the correct libtool binary gets used. --- check.mak | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/check.mak b/check.mak index 847f3f2..01702c3 100644 --- a/check.mak +++ b/check.mak @@ -43,7 +43,7 @@ LOOPS = 10 $(TESTS_ENVIRONMENT) \ CK_DEFAULT_TIMEOUT=360 \ G_SLICE=always-malloc \ - libtool --mode=execute \ + $(LIBTOOL) --mode=execute \ $(VALGRIND_PATH) -q \ $(foreach s,$(SUPPRESSIONS),--suppressions=$(s)) \ --tool=memcheck --leak-check=full --trace-children=yes \ @@ -60,7 +60,7 @@ LOOPS = 10 $(TESTS_ENVIRONMENT) \ CK_DEFAULT_TIMEOUT=360 \ G_SLICE=always-malloc \ - libtool --mode=execute \ + $(LIBTOOL) --mode=execute \ $(VALGRIND_PATH) -q \ $(foreach s,$(SUPPRESSIONS),--suppressions=$(s)) \ --tool=memcheck --leak-check=full --trace-children=yes \ @@ -77,7 +77,7 @@ LOOPS = 10 %.gdb: % $(TESTS_ENVIRONMENT) \ CK_FORK=no \ - libtool --mode=execute \ + $(LIBTOOL) --mode=execute \ gdb $* # torture tests -- 2.7.4