I don't know. The URL offered hands back a 404. errno.c exists in that
dir, but no errno.h that I can find. Since my TiBook is no more, I
can't check much :(
I can speculate, however, that you need to compile your Numeric
libraries (they're C, right?) with -D_REENTRANT or something in order to
Well.. that's good news! (I think!) So.. any idea how to find out what
"resource" is temporarily unavailable?
thanks,
-steve
On Monday, February 25, 2002, at 07:14 PM, Jorge Acereda Maciá wrote:
> Gordon Messmer <[EMAIL PROTECTED]> writes:
>> Well, if the errno is coming from a different threa
Gordon Messmer <[EMAIL PROTECTED]> writes:
> 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 t
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
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
Your code doesn't look like it's using threads... I missed the early
part of this thread. Did you say that this problem is OS X specific,
for sure?
On Sun, 2002-02-24 at 22:12, Steve Spicklemire wrote:
> Nope.. no help. It's looking like the problem might be that errno is
> being set in one th
Nope.. no help. It's looking like the problem might be that errno is
being set in one thread, and detected in another. Does that sound
possible?
thanks,
-steve
On Sunday, February 24, 2002, at 04:55 PM, Gordon Messmer wrote:
> Attempting to write to a full, non-blocking fd might do it. What
Attempting to write to a full, non-blocking fd might do it. What
happens if you direct stdout to /dev/null?
On Sun, 2002-02-24 at 09:46, Steve Spicklemire wrote:
> Hi Folks,
>
> I thought I'd try the fink list this is a follow-up to a question I
> posted yesterday. I've been digging a lit
Hi Folks,
I thought I'd try the fink list this is a follow-up to a question I
posted yesterday. I've been digging a little deeper. What sorts of
things cause "resource temporarily unavailable"?
thanks,
-steve
Begin forwarded message:
> From: Steve Spicklemire <[EMAIL PROTECTED]>
> Date:
