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 847f3f2147903ed43f5d8918483aac3d507e947b..01702c30fe0427445550a6725a5fc45fa7ec3ba0 100644 (file)
--- 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