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 neologix
Recipients nadeem.vawda, neologix, rpointel, vstinner
Date 2011-08-31.18:48:49
SpamBayes Score 1.2549495e-05
Marked as misclassified No
Message-id <1314816530.45.0.895163027519.issue12871@psf.upfronthosting.co.za>
In-reply-to
Content
There's no reason to disable sched_get_priority_(min|max) when Python is built without threads: those libraries control the scheduling policy, and should be available even without pthread.
However, it's really likely that pthread has its own implementation (especially since OpenBSD's threads are implemented in user-space), and it seems that OpenBSD sched_get_priority() is only defined for threads:
http://www.openbsd.org/cgi-bin/man.cgi?query=sched_get_priority_max&apropos=0&sektion=0&manpath=OpenBSD+Current&arch=i386&format=html
"""
This implementation does not support process scheduling.
"""

For example, the following snippet builds correctly on Linux:

"""
#include <sched.h>


int main(int argc, char *argv[])
{
    int (*fp)(int) = sched_get_priority_max;

    return 0;
}
"""

So this should be skipped only on OpenBSD, or we should add some checks to the configure script.
History
Date User Action Args
2011-08-31 18:48:50neologixsetrecipients: + neologix, vstinner, nadeem.vawda, rpointel
2011-08-31 18:48:50neologixsetmessageid: <1314816530.45.0.895163027519.issue12871@psf.upfronthosting.co.za>
2011-08-31 18:48:49neologixlinkissue12871 messages
2011-08-31 18:48:49neologixcreate