[issue19027] undefined symbol: _PyParser_Grammar

Irit Katriel added the comment: We no longer have GRAMMAR_H or _PyParser_Grammar in the code. -- nosy: +iritkatriel resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue19027] undefined symbol: _PyParser_Grammar

Martin Panter added the comment: The same $(GRAMMAR_H) dependency and touch command still exists today, so I suspect this is still valid (though I didn’t try to reproduce it). I think we need to figure out if you can write a proper makefile rule that handles a single command that updates two t

[issue19027] undefined symbol: _PyParser_Grammar

Ned Deily added the comment: BTW, this can be worked around (for non cross-builds at least) by running "make touch" on the source directory, e.g.: make -C python/src -f python/build/Makefile touch But it should be fixed. Doko? -- ___ Python tr

[issue19027] undefined symbol: _PyParser_Grammar

Ned Deily added the comment: It looks like this was caused by the changes for Issue14321 to not run pgen for cross builds. -- nosy: +doko ___ Python tracker ___

[issue19027] undefined symbol: _PyParser_Grammar

Changes by Ned Deily : -- components: +Build nosy: +ned.deily versions: +Python 3.3, Python 3.4 ___ Python tracker ___ ___ Python-bugs

[issue19027] undefined symbol: _PyParser_Grammar

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue19027] undefined symbol: _PyParser_Grammar

New submission from Armin Rigo: It is possible to get the working copy of Python 2.7 in a state such that any attempt to do "make" ends with the error shown in the title. The working copy is perfectly valid; it is a matter of getting the wrong timestamps on the files. (Despite the error messa