Message 113763 - Python tracker

➜

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	mark.dickinson
Recipients	jnoller, mark.dickinson, pitrou, ronaldoussoren
Date	2010-08-13.13:04:31
SpamBayes Score	0.0029786755
Marked as misclassified	No
Message-id	<1281704673.63.0.711322745202.issue9586@psf.upfronthosting.co.za>
In-reply-to

Content
See also: http://paulbeachsblog.blogspot.com/2007/12/building-firebird-20x-macos-semaphoreh.html It looks as though SEM_FAILED is defined as -1 on OS X 10.4, and (sem_t )-1 on OS X 10.5+, so it's really a bug in the OS X header file. Possible workarounds: (1) write (sem_t )SEM_FAILED everywhere in the multiprocessing code (2) define a PY_SEM_FAILED macro and use that (3) don't worry, be happy; i.e., just ignore these warnings on OS X 10.4, content that they're not a real problem (provided we're not trying to compile with a C++ compiler, that is).

See also:

http://paulbeachsblog.blogspot.com/2007/12/building-firebird-20x-macos-semaphoreh.html

It looks as though SEM_FAILED is defined as -1 on OS X 10.4, and (sem_t *)-1 on OS X 10.5+, so it's really a bug in the OS X header file.  Possible workarounds:

(1) write (sem_t *)SEM_FAILED everywhere in the multiprocessing code
(2) define a PY_SEM_FAILED macro and use that
(3) don't worry, be happy;  i.e., just ignore these warnings on OS X 10.4, content that they're not a real problem (provided we're not trying to compile with a C++ compiler, that is).

History
Date	User	Action	Args
2010-08-13 13:04:33	mark.dickinson	set	recipients: + mark.dickinson, ronaldoussoren, pitrou, jnoller
2010-08-13 13:04:33	mark.dickinson	set	messageid: <1281704673.63.0.711322745202.issue9586@psf.upfronthosting.co.za>
2010-08-13 13:04:32	mark.dickinson	link	issue9586 messages
2010-08-13 13:04:31	mark.dickinson	create