[issue1722225] Build on QNX 6

Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- resolution: -> accepted status: open -> closed _ Tracker <[EMAIL PROTECTED]> _ __

[issue1722225] Build on QNX 6

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Thanks for the patch. Committed as r63562. _ Tracker <[EMAIL PROTECTED]> _ ___ Python-b

[issue1722225] Build on QNX 6

Matt Kraai added the comment: Regarding the curses issue, I removed that portion of the patch and the curses module still compiled. It must have been an artifact from before I disabled _XOPEN_SOURCE. Thanks for catching that. Regarding the stack size, without the "-N 2048K" option, "make test"

[issue1722225] Build on QNX 6

Vladimir Konjkov added the comment: there is script Misk/find_recursionlimit.py that can help to find real recursion limit for QNX4 for one recursion used ~900 kb of stack thus 1Mb sufficient for default recursion limit = 1000. _ Tracker <[EMAIL PROTECTED]>

[issue1722225] Build on QNX 6

Vladimir Konjkov added the comment: For _XOPEN_SOURCE and _XOPEN_SOURCE_EXTENDED look this http://opengroup.org/onlinepubs/007908775/xcurses/implement.html _ Tracker <[EMAIL PROTECTED]>

[issue1722225] Build on QNX 6

Martin v. Löwis added the comment: I don't understand the ncurses issue: you already disable the definition of _XOPEN_SOURCE in the patch, hence _XOPEN_SOURCE_EXTENDED does not get defined, hence ncurses should not define wchar_t. So what's the actual problem that this fragment solves? As for std

[issue1722225] Build on QNX 6

Matt Kraai added the comment: This patch contains two improvements over the previous version: * it uses configure to check whether sys/termio.h is available and uses the result to determine whether to include it and * it makes malloc_closure.c use _SC_PAGESIZE instead of getpagesize if it's av

[issue1722225] Build on QNX 6

Martin v. Löwis added the comment: Thanks for the explanation; that makes sense (I didn't expect that the value of these constants depends on the size of some structure, normally, they are "truly" constant, e.g. 0x5405 on Linux). The autoconf test should check whether the header (sys/termio.h) i

[issue1722225] Build on QNX 6

Matt Kraai added the comment: If they're defined, TCGETA, TCSETA, TCSETAW, and TCSETAF are used on lines 702, 714, 717, and 720 of Modules/termios.c as of r60219. They are defined by sys/ioctl.h as #define TCGETA _IOR('T', 1, struct termio) #define TCSETA _IOW('T', 2, struct

[issue1722225] Build on QNX 6

Guido van Rossum added the comment: I think it's fine to accept this (once the remaining issues are resolved) -- it's a remarkably small patch. Regarding TCGETA, perhaps the issue is that it isn't defined unless is included? While Python doesn't USE it, it exports it fro the termios module, if

[issue1722225] Build on QNX 6

Matt Kraai added the comment: I'm not interested in QNX 4, as that's not what I use. I'd be willing to supporting threads on QNX 6. -- title: Build on QNX -> Build on QNX 6 _ Tracker <[EMAIL PROTECTED]> _

[issue1722225] Build on QNX

Vladimir Konjkov added the comment: willing you implement thread support for qnx6, or may be qnx4? _ Tracker <[EMAIL PROTECTED]> _ ___ Python-

[issue1722225] Build on QNX

Matt Kraai added the comment: I'm willing to maintain the QNX 6 port, but I can't promise that I'll be able to do so for 5 years. I don't know if that's sufficient or not. _ Tracker <[EMAIL PROTECTED]> ___

[issue1722225] Build on QNX

Martin v. Löwis added the comment: I still don't get the point of including sys/termio.h. Python does *not* use the TCGETA macro itself *at all*. Python applications may, but they can't use the included sys/termio.h, since they are written in Python, not in C. To put the question the other way: I

[issue1722225] Build on QNX

Vladimir Konjkov added the comment: addition TCGETA is a constant. That's right! under QNX4 TCGETA defined as MACRO in . That's right! in Modules/termios.c there's #include That's right too! What's problem after all? Problem is that MACRO definition of TCGETA need sizeof(struct termio), that's (

[issue1722225] Build on QNX

Vladimir Konjkov added the comment: However, I don't understand this entire point: What do you mean by "using TCGETA requires that struct termio be defined"? How is TCGETA defined to produce such a dependency? TCGETA is a constant, right? --

[issue1722225] Build on QNX

Vladimir Konjkov added the comment: look this http://www.mail-archive.com/python-bugs-list%40python.org/msg07749.html it's for python-2.3.5 under qnx4.25. about pyport.h under qnx4.25: I include "unix.h" instead of definition of function openpty()+forkpty() in pyport.h, openpty()+forkpty() natu

[issue1722225] Build on QNX

Martin v. Löwis added the comment: A 2.5 patch would not be accepted; there won't be any new features for 2.5 , and new port would be a new feature. Procedurally, are you willing to support a QNX port for the coming years (say, 5 years)? Otherwise, there is little point in accepting such a port