[issue3110] Multiprocessing package build problem on Solaris 10

Jesse Noller added the comment: Additional protection checked in in r71022 -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue3110] Multiprocessing package build problem on Solaris 10

osvenskan added the comment: I'm facing the same problem (getting a good definition of SEM_VALUE_MAX) for my posix_ipc extension. The patch presented here will get the compiler to shut up on OpenSolaris, but not for the reason you think. At least, that's the way I see it. On OpenSolaris (2008.0

[issue3110] Multiprocessing package build problem on Solaris 10

Changes by osvenskan : -- nosy: +osvenskan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue3110] Multiprocessing package build problem on Solaris 10

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: According to POSIX, if no determinate value for SEM_VALUE_MAX can be given, the actual value should be queried with sysconf(_SC_SEM_VALUE_MAX), and SEM_VALUE_MAX should not be defined; this is in particular the case when the value depends on

[issue3110] Multiprocessing package build problem on Solaris 10

Jesse Noller <[EMAIL PROTECTED]> added the comment: I've committed the patch in r66184 on trunk, 66185 py3k. Skip raises a good point, therefore I'll leave this open but lower from a blocker. -- priority: release blocker -> high ___ Python tracker <[

[issue3110] Multiprocessing package build problem on Solaris 10

Jesse Noller <[EMAIL PROTECTED]> added the comment: Skip - Richard has been unavailable a good chunk of the summer. I don't know when he will be online again. ___ Python tracker <[EMAIL PROTECTED]> __

[issue3110] Multiprocessing package build problem on Solaris 10

Skip Montanaro <[EMAIL PROTECTED]> added the comment: I can confirm that Jesse's patch allows multiprocessing to compile on Solaris 10. Note, however, that there are other symbolic constants defined which contain "SEM_VALUE_MAX", all with widely differing underlying values: % find /usr/incl

[issue3110] Multiprocessing package build problem on Solaris 10

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: I recompiled and tested multiprocessing both under Windows and Linux with this patch, no problems detected. +1 for applying it. ___ Python tracker <[EMAIL PROTECTED]>

[issue3110] Multiprocessing package build problem on Solaris 10

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list

[issue3110] Multiprocessing package build problem on Solaris 10

Jesse Noller <[EMAIL PROTECTED]> added the comment: Anyone mind reviewing the attached patch? This should resolve the solaris compile issue. I used skip's suggested code - I removed the #ifdef solaris at AP's suggestion. -- keywords: +patch Added file: http://bugs.python.org/file11361/

[issue3110] Multiprocessing package build problem on Solaris 10

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: I suggest committing a patch which falls back to _SEM_VALUE_MAX and see how the Solaris buildbot reacts. ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3110] Multiprocessing package build problem on Solaris 10

Jesse Noller <[EMAIL PROTECTED]> added the comment: Raising this to RB, we should not RC without the MP module properly compiling -- priority: high -> release blocker ___ Python tracker <[EMAIL PROTECTED]> _

[issue3110] Multiprocessing package build problem on Solaris 10

Antoine Pitrou <[EMAIL PROTECTED]> added the comment: FWIW, this is what I find on a Solaris box. ./sys/param.h:#define _SEM_VALUE_MAX INT_MAX ./sys/sysconfig.h:#define _CONFIG_SEM_VALUE_MAX 21 /* max. value a semaphore may have */ ./sys/unistd.h:#define _SC_SEM_VALUE_MA

[issue3110] Multiprocessing package build problem on Solaris 10

Changes by Jesse Noller <[EMAIL PROTECTED]>: -- assignee: -> jnoller ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue3110] Multiprocessing package build problem on Solaris 10

Skip Montanaro <[EMAIL PROTECTED]> added the comment: Jesse> Per skip's email: Jesse> FWIW, it appears that Solaris doesn't define SEM_VALUE_MAX but does Jesse> define Jesse> _SEM_VALUE_MAX in sys/params.h. ... Thanks for submitting the bug report. I wonder why the processing

[issue3110] Multiprocessing package build problem on Solaris 10

New submission from Jesse Noller <[EMAIL PROTECTED]>: Per skip's email: FWIW, it appears that Solaris doesn't define SEM_VALUE_MAX but does define _SEM_VALUE_MAX in sys/params.h. .../Modules/_multiprocessing/multiprocessing.c: In function 'init_multiprocessing': .../Modules/_multiprocess