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.

diff --git a/.Sanitize b/.Sanitize
index c51ba683c134320040c4d0bf302006a821b8ecf7..016d6b2207c5e78fabc8ff1e87867c4c9c47f554 100644 (file)
--- 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 4774c504f166573c506af544401d5b6342de199e..d51906e4ba2315d371e5fcb299855a9a4523b065 100644 (file)
--- 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