New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiprocessing package build problem on Solaris 10 #47360
Comments
Per skip's email: .../Modules/_multiprocessing/multiprocessing.c: In function On Windows the author simple #defines SEM_VALUE_MAX to be LONG_MAX. I #ifndef SEM_VALUE_MAX
# ifdef _SEM_VALUE_MAX
# define SEM_VALUE_MAX _SEM_VALUE_MAX
# else
# define SEM_VALUE_MAX INT_MAX
# endif
#endif |
Jesse> Per skip's email:
Thanks for submitting the bug report. I wonder why the processing module Skip |
FWIW, this is what I find on a Solaris box. ./sys/param.h:#define _SEM_VALUE_MAX INT_MAX |
Raising this to RB, we should not RC without the MP module properly |
I suggest committing a patch which falls back to _SEM_VALUE_MAX and see |
Anyone mind reviewing the attached patch? This should resolve the solaris |
I recompiled and tested multiprocessing both under Windows and Linux |
I can confirm that Jesse's patch allows multiprocessing to compile on
How do we know that _SEM_VALUE_MAX is the proper rvalue to use when Richard, as the author of the original processing module do you have |
Skip - Richard has been unavailable a good chunk of the summer. I don't |
I've committed the patch in r66184 on trunk, 66185 py3k. Skip raises a |
According to POSIX, if no determinate value for SEM_VALUE_MAX can be Now, it is not plausible why SEM_VALUE_MAX should vary by installation, IOW, I think the patch is fine as it stands. If you are over-cautious, If you do make this change, please stop using Py_BuildValue to convert a |
I'm facing the same problem (getting a good definition of SEM_VALUE_MAX) On OpenSolaris (2008.05 is what I'm testing with), _SEM_VALUE_MAX is #if (defined(_KERNEL) || defined(_KMEMUSER))
Since multiprocessing.c doesn't #define either of these, both IMHO, given the choice between #defining _KERNEL or _KMEMUSER and I did a survey of all the operating systems to which I have access |
Additional protection checked in in r71022 |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: