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 349b814..8451445 100644
--- a/Makefile.pre.in
+++ b/Makefile.pre.in
@@ -1190,7 +1190,7 @@
-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 8c24653..1ab8581 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -112,6 +112,12 @@
- 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?
================================