aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFred Fish <fnf@specifix.com>1994-01-24 19:36:12 +0000
committerFred Fish <fnf@specifix.com>1994-01-24 19:36:12 +0000
commiteecef7ef065349e02dee4ae37535de8f9ee39985 (patch)
tree38e5fe36e385a6c7f489f89f05487842a558377d
parent2ef7731dee7bfbe8a052f98bb0a2e0b00a3f0460 (diff)
downloadgdb-eecef7ef065349e02dee4ae37535de8f9ee39985.zip
gdb-eecef7ef065349e02dee4ae37535de8f9ee39985.tar.gz
gdb-eecef7ef065349e02dee4ae37535de8f9ee39985.tar.bz2
Since gdb distributions must be sanitized, and it is easy to forget to
run Sanitize during the build process, cause the distribution build process to emit a appropriate message and quit when run in an unsanitized tree.
-rw-r--r--.Sanitize11
-rw-r--r--Makefile.in3
2 files changed, 14 insertions, 0 deletions
diff --git a/.Sanitize b/.Sanitize
index c51ba68..016d6b2 100644
--- a/.Sanitize
+++ b/.Sanitize
@@ -119,6 +119,17 @@ else
verbose=
fi
+# Remove "sanitize-Sanitize" lines.
+if [ -n "${verbose}" ] ; then
+ echo Cleaning unconditional sanitizations out of Makefile.in...
+fi
+cp Makefile.in new
+sed '/start\-sanitize\-Sanitize/,/end-\sanitize\-Sanitize/d' < Makefile.in > new
+if [ -n "${safe}" -a ! -f .Recover/Makefile.in ] ; then
+ mv Makefile.in .Recover
+fi
+mv new Makefile.in
+
if [ -n "${verbose}" ] ; then
echo Looking for signs of \"v9\"...
fi
diff --git a/Makefile.in b/Makefile.in
index 4774c50..d51906e 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -974,6 +974,9 @@ GDB_SUPPORT_FILES= $(GDB_SUPPORT_DIRS)
.PHONY: setup-dirs-gdb gdb.tar.gz make-gdb.tar.gz
setup-dirs-gdb:
+ $(start-sanitize-Sanitize)
+ @if [ -f .Sanitize ] ; then echo "RUN Sanitize FIRST!" ; false ; fi ;
+ $(end-sanitize-Sanitize)
./configure sun4
$(MAKE) clean
./configure -rm sun4