GNU coding guidelines say that ``make check`` should verify the build. That

clashes with what Python's build target did. Rename the target to 'patchcheck'
to avoid the culture clash.

Closes issue 3758.
Reviewed by Benjamin Peterson.

diff --git a/Makefile.pre.in b/Makefile.pre.in
index 349b8148184563d1ae28b8b5167ed3a9229f3225..8451445fefba9a39cac471824d127cb58d2e0593 100644 (file)
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -1190,7 +1190,7 @@ funny:
                -o -print
 
 # Perform some verification checks on any modified files.
-check:
+patchcheck:
        $(RUNSHARED) ./$(BUILDPYTHON) $(srcdir)/Tools/scripts/patchcheck.py
 
 # Dependencies

diff --git a/Misc/NEWS b/Misc/NEWS
index 8c246538a8274cd7ce30fe57cae7e28827f77466..1ab858191889f15c65e3b87f0ab4c7f765a92ae8 100644 (file)
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -112,6 +112,12 @@ Tests
 
 - Issue 3768: Move test_py3kwarn over to the new API for catch_warnings().
 
+Build
+-----
+
+- Issue 3758: Rename the 'check' target to 'patchcheck' so as to not clash with
+  GNU build target guidelines.
+
 
 What's New in Python 2.6 beta 3?
 ================================