➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients xdegaye
Date 2018-01-03.11:29:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514978981.67.0.467229070634.issue32461@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2018-01-03 11:29:41xdegayesetrecipients: + xdegaye
2018-01-03 11:29:41xdegayesetmessageid: <1514978981.67.0.467229070634.issue32461@psf.upfronthosting.co.za>
2018-01-03 11:29:41xdegayelinkissue32461 messages
2018-01-03 11:29:41xdegayecreate