separate out REGISTRY_ENVIRONMENT; we want to use that from our valgrind runs, but...
authorThomas Vander Stichele <thomas@apestaart.org>
Sun, 21 Aug 2005 11:31:40 +0000 (11:31 +0000)
committerThomas Vander Stichele <thomas@apestaart.org>
Sun, 21 Aug 2005 11:31:40 +0000 (11:31 +0000)
Original commit message from CVS:
separate out REGISTRY_ENVIRONMENT; we want to use that from
our valgrind runs, but we also want TESTS_ENVIRONMENT to contain
everything that the first test, gst-register, needs

ChangeLog
check.mak

index 623078b..467592a 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,6 +1,13 @@
 2005-08-21  Thomas Vander Stichele  <thomas at apestaart dot org>
 
        * check.mak:
+         separate out REGISTRY_ENVIRONMENT; we want to use that from
+         our valgrind runs, but we also want TESTS_ENVIRONMENT to contain
+         everything that the first test, gst-register, needs
+
+2005-08-21  Thomas Vander Stichele  <thomas at apestaart dot org>
+
+       * check.mak:
          parse output of valgrind and check for definitely lost, and error
          out; somehow I was led to believe valgrind returns non-zero for
          leaks, but I can't make it do that, so let's parse
index c221a47..90e2089 100644 (file)
--- a/check.mak
+++ b/check.mak
@@ -19,7 +19,7 @@ endif
 
 # valgrind any given test by running make test.valgrind
 %.valgrind: % $(CHECK_REGISTRY)
-       $(TESTS_ENVIRONMENT)                                    \
+       $(REGISTRY_ENVIRONMENT)                                 \
        libtool --mode=execute                                  \
        $(VALGRIND_PATH) -q --suppressions=$(SUPPRESSIONS)      \
        --tool=memcheck --leak-check=yes --trace-children=yes   \