[issue5895] socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED compiles incorrectly

Changes by Christian Heimes : -- resolution: -> out of date stage: test needed -> resolved status: open -> closed ___ Python tracker ___ _

[issue5895] socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED compiles incorrectly

Changes by Adi Roiban : -- nosy: +adiroiban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue5895] socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED compiles incorrectly

Martin v. Löwis added the comment: > Martin: PEP 11 lists platforms no-longer supported, but does not list > those that are. You mean, "doesn't list the platforms that are still supported"? That's on purpose: the point of PEP 11 is to warn current users about forthcoming changes, not to track

[issue5895] socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED compiles incorrectly

Terry J. Reedy added the comment: Naoyuki, unless you can confirm that Daniel's patch works, we will have to close this as out-of-date. Martin: PEP 11 lists platforms no-longer supported, but does not list those that are. For writing/reviewing patches like this, it would be helpful if it did

[issue5895] socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED compiles incorrectly

Daniel Diniz added the comment: Naoyuki, Is the API a mix of size_t and int? Does the attached patch help? If you could confirm that building with _XOPEN_SOURCE_EXTENDED doesn't need a change, the #ifdef should check for that too. -- components: +Build keywords: +patch nosy: +ajaksu2 p

[issue5895] socketmodule.c on HPUX ia64 without _XOPEN_SOURCE_EXTENDED compiles incorrectly

New submission from Naoyuki Tai : Python can build without _XOPEN_SOURCE_EXTENDED on HPUX ia64 but the socket module is bust. This is because APIs like getsockname() do not use socklen_t*. Instead it is defined using int* for some of arguments. In socketmodule.c, it consistently use socklent_t wh