On Mon, 2002-02-25 at 14:47, Steve Spicklemire wrote: > Hi Gordon, > > Yes.. the same code on Linux, and Win32 works OK. I've actually > tracked it down to a problem with threads and Numeric (another fink > module). Here's a message I just sent to the MacPython folks. I'm just > not sure how I can find out what "resource" is "unavailable". Any hints > would be appreciated!
Well, if the errno is coming from a different thread, then OS X, unlike most POSIX OS's, probably doesn't have a separate errno for each thread (which sorta sucks. a lot). Under Linux, for instance, "errno" is a macro which locates the current thread's errno, and returns its value. Without per-thread errno, all kinds of hell await, I'm sure. Applications will have to be extremely tight about checking the return value of system calls and errno, and *hope* to avoid races :) 'Course, that's speculation, and I could be way off base. I no longer have my TiBook, and can't verify that. Can anyone determine whether or not per-thread errno's are used on OS X? Maybe it would help to compile with '-D_REENTRANT'? _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
