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.
This commit is contained in:
parent
187ac1bda4
commit
cdeb24bb05
|
@ -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
|
||||
|
|
|
@ -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?
|
||||
================================
|
||||
|
|
Loading…
Reference in New Issue