[Python-Dev] Re: [Python-checkins] python/dist/src/Python pythonrun.c, 2.161.2.15, 2.161.2.16 (original) (raw)

Kurt B. Kaiser kbk at shore.net
Mon Jan 17 05:01:19 CET 2005

kbk at shore.net (Kurt B. Kaiser) writes:

kbk at shore.net (Kurt B. Kaiser) writes:

[JH]

../Python/symtable.c:193: structure has no member named `sttmpname'

Do you see that? Yeah, the merge eliminated it from the symtable struct in symtable.h. You moved it to symtableentry at rev 2.12 in MAIN :-)

[...]

I checked in a change which adds the st_tmpname element back to symtable. Temporary until someone gets time to evaluate the situation.

[...]

Apparently the (ASTH)(ASTH) (ASTH)(ASTC): target ran and Python-ast.c was recreated (without the changes). It's not clear to me how/why that happened. I did start with a clean checkout, but it seems that the target only runs if Python-ast.c and/or its .h are missing (they should have been in the checkout), or older than Python.asdl, which they are not. I don't see them in the .cvsignore.

I believe the problem was caused by the fact that the dates in the local tree aren't the repository dates, so it happened that Parser/Python.adsl had a newer date than Python-ast.[ch]. I did a clean install on my Debian system and got around the issue by touching Python-ast.[c,h] before the build. IMO ASDLGEN s/b a .phony target, run manually as needed by the AST developer. Otherwise there will be no end of trouble when people try to build from CVS after the merge.

Absent objection, I'll check in such a change.

== The tree compiles, but there is a segfault when make tries to run Python on setup.py. Failure occurs when trying to import site.py

== Neal has fixed the import issue and several others!! I was bitten by the Python.asdl / Python-ast.[ch] timing again when updating to his changes....

Branch now builds and python can be started. There are a number of test failures remaining.

-- KBK

More information about the Python-Dev mailing list