[Python-Dev] RE: POSIX thread code and Cygwin (original) (raw)
Tim Peters tim@zope.com
Fri, 22 Mar 2002 16:16:30 -0500
- Previous message: [Python-Dev] POSIX thread code and Cygwin
- Next message: [Python-Dev] RE: POSIX thread code and Cygwin
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Gerald S. Williams]
I submitted another patch to the POSIX threads code. It is under SourceForge as patch number 533681.
This tells Python to explicitly use the POSIX semaphore code for Cygwin. I had inadvertently left a remnant in my version of thread.c that forced POSIXSEMAPHORES to be defined for Cygwin. It turns out POSIXSEMAPHORES is only set if rtems is defined. At the time I didn't know what that meant but thought it must have been defined since I got the correct code.
I don't understand. If Cygwin requires rtems in order that _POSIX_SEMAPHORES be defined, then either Cygwin has a bug here, or Cygwin needs rtems if you want to use real-time gimmicks like semaphores. In either case, I don't think it's Python's place to second-guess the Cygwin team: report it as a bug to Cygwin, or do whatever they recommend to get rtems defined in the Cygwin build.
- Previous message: [Python-Dev] POSIX thread code and Cygwin
- Next message: [Python-Dev] RE: POSIX thread code and Cygwin
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]