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 | jnoller |
|---|---|
| Recipients | jnoller, roudkerk, skip.montanaro |
| Date | 2008年06月14日.19:36:12 |
| SpamBayes Score | 0.48835927 |
| Marked as misclassified | No |
| Message-id | <1213472177.07.0.795399068376.issue3110@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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/_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 used a little cpp action to define it: #ifndef SEM_VALUE_MAX # ifdef _SEM_VALUE_MAX # define SEM_VALUE_MAX _SEM_VALUE_MAX # else # define SEM_VALUE_MAX INT_MAX # endif #endif |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月14日 19:36:18 | jnoller | set | spambayes_score: 0.488359 -> 0.48835927 recipients: + jnoller, skip.montanaro, roudkerk |
| 2008年06月14日 19:36:17 | jnoller | set | spambayes_score: 0.488359 -> 0.488359 messageid: <1213472177.07.0.795399068376.issue3110@psf.upfronthosting.co.za> |
| 2008年06月14日 19:36:15 | jnoller | link | issue3110 messages |
| 2008年06月14日 19:36:14 | jnoller | create | |