Mark Dickinson <dicki...@gmail.com> added the comment: 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). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9586> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
