[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: setitimer with Cygwin and Hurd
From: |
Andy Wingo |
Subject: |
Re: setitimer with Cygwin and Hurd |
Date: |
Tue, 07 Mar 2017 15:37:53 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
On Tue 07 Mar 2017 15:31, Mike Gran <address@hidden> writes:
>>> On Hurd, calls to setitimer and getitimer for the profiling
>>> and virtual timers will always fail with ENOSYS.
>>> On Cygwin, calls to setitimer and getitimer for the
>>> profiling and virtual timers will always fail with EINVAL.
>
>>Is it possible to avoid defining these interfaces if they will never
>>work?
>
>>Is that even a good idea? :) Maybe not. Would be better to have
>>(defined? 'setitimer) or so. If not, a setitimer feature I guess --
>>(provided? 'setitimer).
> This is what I came up with
> branch wip-itimer-checks
> commit f5b362586d7622c408d4402c7cb496c45ffb56e8
> What do you think?
Looks great. Thank you, please push!
Andy