From ecfa394fe3bf4ef27d72fcab170bc860cfc142f5 Mon Sep 17 00:00:00 2001
From: Alex Rousskov <rousskov@measurement-factory.com>
Date: Sun, 2 May 2010 12:09:21 -0600
Subject: [PATCH] Do not stop on the first error to be compatible with "make -k
 check".

If we stop on the first error, it becomes very difficult to test your
changes with "make check" when somebody else broke some other code.
---
 test-suite/testheaders.sh | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/test-suite/testheaders.sh b/test-suite/testheaders.sh
index 457496a12e..7927fe0d38 100755
--- a/test-suite/testheaders.sh
+++ b/test-suite/testheaders.sh
@@ -16,6 +16,8 @@ else
 	dir="${2}"
 fi
 
+exitCode=0
+
 for f in `cd ${dir} && ls -1 *.h 2>/dev/null`; do
 	echo -n "Testing ${dir}/${f} ..."
 	hdr=`echo "${f}" | sed s/.h//`
@@ -32,11 +34,14 @@ for f in `cd ${dir} && ls -1 *.h 2>/dev/null`; do
 	fi
 	if [ ! -f testHeaderDeps_${hdr}.o ]; then
 		rm testHeaders
-		exit 1
-	fi
+		exitCode=1
+	else
 	echo "OK."
 	# unit-tests require an app to run.
 	# our most-recent object suits this purpose.
 	# let's link or some tests will fail
 	${cc} ./testHeaderDeps_${hdr}.o -o ./testHeaders
+	fi
 done
+
+exit $exitCode
-- 
2.47.3