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 skip.montanaro
Recipients jnoller, pitrou, roudkerk, skip.montanaro
Date 2008-09-03.18:22:07
SpamBayes Score 4.00435e-05
Marked as misclassified No
Message-id <>
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/include -name '*.h' | xargs egrep SEM_VALUE_MAX
    /usr/include/sys/param.h:#define        _SEM_VALUE_MAX          INT_MAX
    /usr/include/sys/sysconfig.h:#define    _CONFIG_SEM_VALUE_MAX   21 
    /* max. value a semaphore may have */
    /usr/include/sys/unistd.h:#define       _SC_SEM_VALUE_MAX          
    /usr/include/limits.h:#define   _POSIX_SEM_VALUE_MAX    32767

How do we know that _SEM_VALUE_MAX is the proper rvalue to use when
#define-ing SEM_VALUE_MAX?

Richard, as the author of the original processing module do you have
something to contribute to this discussion?  You've been completely
silent on this issue.
Date User Action Args
2008-09-03 18:22:09skip.montanarosetrecipients: + skip.montanaro, pitrou, roudkerk, jnoller
2008-09-03 18:22:09skip.montanarosetmessageid: <>
2008-09-03 18:22:08skip.montanarolinkissue3110 messages
2008-09-03 18:22:07skip.montanarocreate