New submission from Andy <[EMAIL PROTECTED]>: With a clean checkout of the py3k source it fails to build the Parser exension module (based on Modules/parsermodule.c) when building against a cygwin target.
This appears to be related to the movement of the symbol _PyParser_Grammar from graminit.c to Parser\metagrammar.c. (At least this is where it was going by the code comments) Because of this the module now requires Parser\metagrammar.c to get this information via Py_meta_grammar. The patch modifies setup.py to add the required file and modifies parsermodule.c to use the accessor function. (This fails on a clean trunk build in the same way as well - which makes me very suspicious that this is not a "real" issue as the buildbots seem to be green.) My gut feeling is that my modification to setup.py for the module is incorrect - it just looks messy. So I await the inevitable: "That's not how to fix it...." :-) ---------- components: Extension Modules files: parsermodule_fix.diff keywords: patch messages: 75603 nosy: kirkshorts severity: normal status: open title: Module 'parser' fails to build type: compile error versions: Python 3.0 Added file: http://bugs.python.org/file11960/parsermodule_fix.diff _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4279> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
