[issue17391] _cursesmodule Fails to Build on GCC 2.95 (static)
Charles-François Natali added the comment: Jerrfey, thanks for your patch, but apparently in the - long - meantime, the declaration has already been moved up. -- nosy: +neologix resolution: - out of date stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17391 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17391] _cursesmodule Fails to Build on GCC 2.95 (static)
Jeffrey Armstrong added the comment: Next time I see a bug I'll be sure to wait rather than actually submit a patch... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17391 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17391] _cursesmodule Fails to Build on GCC 2.95 (static)
Charles-François Natali added the comment: Jeffrey Armstrong added the comment: Next time I see a bug I'll be sure to wait rather than actually submit a patch... I understand your frustration, but please don't do that: you have to understand that we don't have any automatic reminder of issues, so it can happen that some go unnoticed, especially if no core developer is assigned. Is this happens in the future, simply send an email on the python-dev mailing list saying that you've got a patch waiting for review, this shoud do the trick. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17391 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17391] _cursesmodule Fails to Build on GCC 2.95 (static)
Mark Lawrence added the comment: Can we have a review of the one line patch please. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17391 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17391] _cursesmodule Fails to Build on GCC 2.95 (static)
New submission from Jeffrey Armstrong: When compiling Modules/_cursesmodule.c as a static module with GCC 2.95.3, an error is encountered on line 2260 in PyCurses_GetWin. The error occurs because the PyCursesInitialised macro appears prior _Py_IDENTIFIER(read), which is actually a variable declaration. Switching the order of the statements fixes the issue. In all other functions within Modules/_cursesmodule.c, PyCursesInitialised always appears after all variable declarations. This bug was encountered on the platform m68k-atari-mint using Python 3.3.0 and GCC 2.95.3. -- components: Build files: curses.patch keywords: patch messages: 183877 nosy: Jeffrey.Armstrong priority: normal severity: normal status: open title: _cursesmodule Fails to Build on GCC 2.95 (static) type: compile error versions: Python 3.3 Added file: http://bugs.python.org/file29365/curses.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17391 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17391] _cursesmodule Fails to Build on GCC 2.95 (static)
Changes by Jeffrey Armstrong jeffrey.armstr...@approximatrix.com: -- components: +Extension Modules -Build ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17391 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
