Sridhar Ratnakumar <sridh...@activestate.com> added the comment: On 2010-05-31, at 4:54 PM, John Levon wrote:
> In terms of getting Python building again, it should be sufficient to define > _XPG4_2 for the multiprocessing module compile only. I can verify that the following patch works around this issue (for now); --- python.org/Modules/_multiprocessing/multiprocessing.c 2010-05-31 17:04:08.499559243 -0700 +++ python/Modules/_multiprocessing/multiprocessing.c 2010-05-31 17:04:28.568723434 -0700 @@ -6,6 +6,11 @@ * Copyright (c) 2006-2008, R Oudkerk --- see COPYING.txt */ +/* + * Workaround for http://bugs.python.org/issue8864#msg106820 + */ +#define _XPG4_2 + #include "multiprocessing.h" #ifdef SCM_RIGHTS On 2010-06-01, at 5:25 AM, John Levon wrote: > Right, it should be one of the "official" ways of enabling that. So I presume this should be the right way to fix this bug? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8864> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
