Add a test that all programs in the bindist were built with the right GHC
authorIan Lynagh <igloo@earth.li>
Fri, 10 Dec 2010 16:12:18 +0000 (16:12 +0000)
committerIan Lynagh <igloo@earth.li>
Fri, 10 Dec 2010 16:12:18 +0000 (16:12 +0000)
They should use the GHC from the build tree, not the bootstrapping compiler.

bindisttest/checkBinaries.sh [new file with mode: 0644]
bindisttest/ghc.mk

diff --git a/bindisttest/checkBinaries.sh b/bindisttest/checkBinaries.sh
new file mode 100644 (file)
index 0000000..3c62198
--- /dev/null
@@ -0,0 +1,20 @@
+#!/bin/sh
+
+echo "1 is $1 done"
+EXPECTED_VERSION="$1"
+
+# Our shared libraries are currently executable (is that a bug?), so
+# we exclude anything that looks like a shared library
+for f in `find bindisttest/a/b/c -type f -executable ! -name '*.so' ! -name '*.dynlib' ! -name '*.dll'`
+do
+    if grep -q '("GHC RTS", "YES")' "$f"
+    then
+        # Looks like a GHC executable. Is it for the right version?
+        THIS_VERSION=`./$f +RTS --info | grep '"GHC version"' | sed -e 's/^ ,("GHC version", "//' -e 's/")$//'`
+        if [ "$THIS_VERSION" != "$EXPECTED_VERSION" ]
+        then
+            echo "Bad GHC version '$THIS_VERSION' for '$f'" >&2
+            exit 1
+        fi
+    fi
+done
index 4be2166..a3e97b0 100644 (file)
@@ -31,6 +31,7 @@ test_bindist:
 # c:/foo is a remote file), so it's safer to bzip and then pipe into
 # tar rather than using tar -xjf:
        cd bindisttest/a/b/c/ && $(BZIP2_CMD) -cd ../../../../$(BIN_DIST_TEST_TAR_BZ2) | $(TAR_CMD) -xf -
+       $(SHELL) bindisttest/checkBinaries.sh $(ProjectVersion)
 ifeq "$(Windows)" "YES"
        mv bindisttest/a/b/c/$(BIN_DIST_NAME) $(BIN_DIST_INST_DIR)
 else