From: Jan Schmidt <thaytan@noraisin.net>
Date: Mon, 12 Oct 2009 13:37:15 +0000 (+0100)
Subject: check: Use the LIBTOOL env var rather than hard-coding
X-Git-Tag: upstream/20130618~190
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=6380d4b370f078f0cca7240428ea9f6639571ff5;p=platform%2Fupstream%2Fgst-common.git

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.
---

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