➜

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 martin.panter
Recipients Marc Duponcheel, Trevor.Bowen, gregory.p.smith, martin.panter, pitrou, r.david.murray
Date 2016-07-13.02:37:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1468377469.03.0.553313001511.issue19142@psf.upfronthosting.co.za>
In-reply-to
Content 
Since 2.7.12 and 3.5.2, pgen should not be executed when in cross-compilation mode, thanks to Issue 22359 and Issue 22625. So I suspect the main problem is basically solved now.

Even though it should no longer be used, pgen is still cross-compiled depending on the timestamps and “make touch”. (Evidence: 
Issue 27490.)

My guess of why “make touch” did not work for Trevor was that he was compiling Python 2. In this case, “make touch” was added in revision da3f4774b939, and still only affects two files, neither of which are generated by pgen. Maybe Python 2’s “make touch” rule could be expanded for other generated files including Include/graminit.h etc.
History
Date User Action Args
2016-07-13 02:37:49martin.pantersetrecipients: + martin.panter, gregory.p.smith, pitrou, r.david.murray, Trevor.Bowen, Marc Duponcheel
2016-07-13 02:37:49martin.pantersetmessageid: <1468377469.03.0.553313001511.issue19142@psf.upfronthosting.co.za>
2016-07-13 02:37:48martin.panterlinkissue19142 messages
2016-07-13 02:37:48martin.pantercreate