[issue32461] the first build after a change to Makefile.pre.in uses the old Makefile

[Xavier de Gaye]

Xavier de Gaye <xdegaye at gmail.com> added the comment:

Two problems:
* It is not clear whether one should re-run make after the Makefile file has been updated since the (stale when not using GNU make) Makefile is run to completion.
* The 'Makefile' target is remade twice when Makefile.pre.in has been changed. The 'Makefile.pre' target is a pre-requisite of only the 'Makefile' target which means that if 'Makefile.pre' is being remade then 'Makefile' will be remade next and so it is useless to run the 'Makefile' target in a sub-make within the 'Makefile.pre' target.

The implementation of the uploaded stale-makefile.patch aborts the build when 'Makefile' has been remade and we are not running GNU make. It also removes the useless sub-make in the 'Makefile.pre' target.

----------
Added file: https://bugs.python.org/file47362/stale-makefile.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32461>
_______________________________________