[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: interix 3.5 select bug
From: |
Jim Meyering |
Subject: |
Re: interix 3.5 select bug |
Date: |
Wed, 11 Mar 2009 15:00:39 +0100 |
Simon Josefsson wrote:
> Jim Meyering <address@hidden> writes:
>
>> + * lib/nanosleep.c (my_usleep): Use 1, not 0, as the first argument.
>> + This avoids a failure on Interix 3.5. Details in
>> + http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/16077
>
> Is this the best solution? It seems that another solution would be to
> detect this problem, and to replace select if the system's select
> doesn't work. Is there anything in POSIX whether this should work or
> not?
I haven't studied the spec enough to say, but now I agree with you.
Using select like that is certainly common practice.
This looks like a job for a replacement function.
However, technically the configure-time test would have
to be one that runs a binary, to determine if select fails
like that. and that's ugly... all of this for interix. humph.
Maybe I'll wait until someone else contributes the module.
- Re: interix 3.5 select bug, Pádraig Brady, 2009/03/11
- Re: interix 3.5 select bug, Jim Meyering, 2009/03/11
- Re: interix 3.5 select bug, Simon Josefsson, 2009/03/11
- Re: interix 3.5 select bug,
Jim Meyering <=
- Re: interix 3.5 select bug, Bruno Haible, 2009/03/12
- Re: interix 3.5 select bug, Jim Meyering, 2009/03/12
- Re: interix 3.5 select bug, Bruno Haible, 2009/03/12
- Re: interix 3.5 select bug, Jim Meyering, 2009/03/13
- Re: interix 3.5 select bug, Bruno Haible, 2009/03/13
- RE: interix 3.5 select bug, Markus Duft, 2009/03/13
- Re: interix 3.5 select bug, Simon Josefsson, 2009/03/16
Re: interix 3.5 select bug, Paolo Bonzini, 2009/03/11
RE: interix 3.5 select bug, Markus Duft, 2009/03/12