➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author srid
Recipients loewis, movement, srid, zooko
Date 2010-06-01.16:12:27
SpamBayes Score 0.03510722
Marked as misclassified No
Message-id <C311201B-4152-48FE-8805-A41FE7C79B61@activestate.com>
In-reply-to <1275350083.23.0.880687640297.issue8864@psf.upfronthosting.co.za>
Content 
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?
History
Date User Action Args
2010-06-01 16:12:29sridsetrecipients: + srid, loewis, zooko, movement
2010-06-01 16:12:27sridlinkissue8864 messages
2010-06-01 16:12:27sridcreate