[New-bugs-announce] [issue3110] Multiprocessing package build problem on Solaris 10

Jesse Noller report at bugs.python.org
Sat Jun 14 21:36:17 CEST 2008

New submission from Jesse Noller <jnoller at gmail.com>:

Per skip's email:
FWIW, it appears that Solaris doesn't define SEM_VALUE_MAX but does 
_SEM_VALUE_MAX in sys/params.h.

   .../Modules/_multiprocessing/multiprocessing.c: In function 
   .../Modules/_multiprocessing/multiprocessing.c:253: error: 
'SEM_VALUE_MAX' undeclared (first use in this function)
   .../Modules/_multiprocessing/multiprocessing.c:253: error: (Each 
undeclared identifier is reported only once
   .../Modules/_multiprocessing/multiprocessing.c:253: error: for each 
function it appears in.)

On Windows the author simple #defines SEM_VALUE_MAX to be LONG_MAX.  I 
a little cpp action to define it:

   #ifndef SEM_VALUE_MAX
   #  ifdef _SEM_VALUE_MAX
   #  else
   #    define SEM_VALUE_MAX INT_MAX
   #  endif

components: Extension Modules
messages: 68210
nosy: jnoller, roudkerk, skip.montanaro
severity: normal
status: open
title: Multiprocessing package build problem on Solaris 10
type: compile error
versions: Python 2.6, Python 3.0

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list