[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Changes by Richard Oudkerk : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ P

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Roundup Robot added the comment: New changeset a5b49db3383d by Richard Oudkerk in branch '3.2': Issue #9586: Redefine SEM_FAILED on MacOSX to keep compiler happy. http://hg.python.org/cpython/rev/a5b49db3383d New changeset a70db584e897 by Richard Oudkerk in branch '3.3': Issue #9586: Merge http:

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Changes by Ned Deily : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mail

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Jesse Noller added the comment: looks fine mark -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Mark Dickinson added the comment: Actually, since SEM_FAILED isn't public and is only used in one file, it seems simplest just to redefine it on Mac. Here's a patch. -- keywords: +patch Added file: http://bugs.python.org/file18505/sem_failed_tiger.patch __

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Jesse Noller added the comment: I agree with Antoine -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Antoine Pitrou added the comment: > (2) define a PY_SEM_FAILED macro and use that That sounds reasonable. -- ___ Python tracker ___ _

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Mark Dickinson added the comment: BTW, as far as I can tell from the standard (see e.g., section 6.5.9p2 of www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf ), comparison between a pointer and an integer gives undefined behaviour, except in the case where the integer can be interpreted as a

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Mark Dickinson 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:

[issue9586] "warning: comparison between pointer and integer" in multiprocessing build on Tiger

Changes by Mark Dickinson : -- title: "warning: comparison between pointer and integer" in multiprocessing build on PPC/Tiger -> "warning: comparison between pointer and integer" in multiprocessing build on Tiger ___ Python tracker