This is from bug www.python.org/sf/1465408 Because the Python.asdl and the generated Python-ast.[ch] get checked into svn in the same revision, the svn export I use to build the tarballs sets them all to the same timestamp on disk (the timestamp of the checkin). "make" then attempts to rebuild the ast files - this requires a python executable. Can you see the bootstrap problem? To "fix" this, I'm going to make the "welease" script that does the releases touch the ast files to set their timestamps newer than that of Python.asdl. It's not an ideal solution, but it should fix the problem. The other option would be some special Makefile magic that detects this case and doesn't rebuild the files if no "python" binary can be found. I have no idea how you'd do this in a portable way. Anyone got other options? Anthony -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4