Author martin.panter
Recipients Arfrever, doko, eric.snow, gregory.p.smith, koobs, loewis, martin.panter, ned.deily, petri.lehtinen, pitrou, python-dev, rpetrov, sbt, trent, vstinner, zach.ware
Date 2016-09-12.04:24:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473654246.15.0.531353190251.issue15819@psf.upfronthosting.co.za>
In-reply-to
Content
Matthias seems to have already applied his patch in Python 3.3 and 3.4+: revision f2cc3d8b88bb.

Roumen: Is your problem still relevant? If so, perhaps open a separate bug to elaborate.

Koobs: Is your problem with finding Python/Python-ast.c still relevant? Is the $(ASDLGEN) makefile rule being run? I tried building both Python 2 and 3 outside the source tree, with Gnu and BSD Make. In all cases, if I hack the timestamps to force $(ASDLGEN) to run and remove the original source Python/Python-ast.c, it is correctly generated and compiled in the build directory. If I hack the timestamps the other way so that $(ASDLGEN) is not run, the file from the source directory is compiled into the build directory. So everything seems to be working reasonably well.
History
Date User Action Args
2016-09-12 04:24:06martin.pantersetrecipients: + martin.panter, loewis, doko, gregory.p.smith, pitrou, vstinner, ned.deily, trent, rpetrov, Arfrever, python-dev, sbt, eric.snow, petri.lehtinen, zach.ware, koobs
2016-09-12 04:24:06martin.pantersetmessageid: <1473654246.15.0.531353190251.issue15819@psf.upfronthosting.co.za>
2016-09-12 04:24:06martin.panterlinkissue15819 messages
2016-09-12 04:24:05martin.pantercreate