[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Ned Deily added the comment: P.P.S. I've updated the OS X installers as of 3.3.0b2 to build and link with a local copy of ncurses 5.9 rather than older Apple-supplied ones. test_curses now passes. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 2035c5ad4239 by Ned Deily in branch 'default': Issue #14225: Fix Unicode support for curses (#12567) on OS X: http://hg.python.org/cpython/rev/2035c5ad4239 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Ned Deily n...@acm.org added the comment: It turns out that the Unicode support for curses did not build correctly on OS X at all. There were two issues: 1. On OS X, unlike many systems, does not supply separate libncurses and libncursesw in /usr/lib; same for libpanel/libpanelw. So the tests in setup.py based on the presence of the w libs failed, thus disabling the wide-char support in the extension modules even though the OS X libs supported it. The tests in setup.py are now fixed to handle building on OS X with either the system libs or locally-supplied copies. 2. The 32-bit-only installer has historically built and supplied its own copy of libncursesw so that installer build did find a wide lib. However, the wide code support within ncurses is conditional depending on _XOPEN_SOURCE_EXTENDED which is specifically not defined for OS X (platform=='darwin') builds. That caused the compile errors (things like cchar_t from the ncurses include files were not getting defined). The solution for that is to supply _XOPEN_SOURCE_EXTENDED locally to the _curses* extension module builds. -- resolution: - fixed stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
STINNER Victor victor.stin...@gmail.com added the comment: Cool, thanks for the fix! -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Ned Deily n...@acm.org added the comment: P.S. All is not perfect. I initially missed re-running test_curses with the system ncurses library on OS X where ncurses is at 5.4 or with the 32-bit-installer which builds ncurses 5.5. When I did, test_curses failed as described in Issue15037. test_curses passes when Python is built with a MacPorts ncurses 5.9. The best solution would be to update the installer builds to build and use the latest ncurses 5.9. That may have to wait until after 3.3.0b1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Georg Brandl ge...@python.org added the comment: And will you fix it for beta1, or do you think it can be done later? BTW, what is the syntax error here? I don't really see it... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Georg Brandl ge...@python.org added the comment: Is this issue still valid? -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
Ned Deily n...@acm.org added the comment: It was still valid as of 3.3.0a4. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14225] _cursesmodule compile error in OS X 32-bit-only installer build
New submission from Ned Deily n...@acm.org: ./Modules/_cursesmodule.c:279: error: syntax error before 'cchar_t' /Users/sysadmin/build/v3.3.0a1/Modules/_cursesmodule.c: In function 'PyCurses_ConvertToCchar_t': ./Modules/_cursesmodule.c:289: error: 'obj' undeclared (first use in this function)/Users/sysadmin/build/v3.3.0a1/Modules/_cursesmodule.c:279: error: syntax error before 'cchar_t' Note to self, this installer build builds its own version of ncurses. It may need adjusting for 3.3. -- assignee: ned.deily components: Build, Macintosh messages: 155130 nosy: ned.deily priority: release blocker severity: normal status: open title: _cursesmodule compile error in OS X 32-bit-only installer build type: compile error versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14225 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
