* setitimer with Cygwin and Hurd
[not found] <1493122235.1719816.1488779191346.ref@mail.yahoo.com>
@ 2017-03-06 5:46 ` Mike Gran
2017-03-06 21:04 ` Andy Wingo
0 siblings, 1 reply; 4+ messages in thread
From: Mike Gran @ 2017-03-06 5:46 UTC (permalink / raw)
To: Guile-devel Development
Hi-
In trying to get Guile master to build on a few
different VMs, I've run into a problem with setitimer and
getitimer for ITIMER_PROF and ITIMER_VIRTUAL.
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.
I figure the way forward is to patch the test suite
so that any tests that require the profiling or virtual
itimers is 'unsupported. But you'd end up with quite a
bit of special casing in a half-dozen of the test scripts.
Anyone have a better suggestion?
-Mike Gran
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: setitimer with Cygwin and Hurd
2017-03-06 5:46 ` setitimer with Cygwin and Hurd Mike Gran
@ 2017-03-06 21:04 ` Andy Wingo
2017-03-07 14:31 ` Mike Gran
0 siblings, 1 reply; 4+ messages in thread
From: Andy Wingo @ 2017-03-06 21:04 UTC (permalink / raw)
To: Mike Gran; +Cc: Guile-devel Development
On Mon 06 Mar 2017 06:46, Mike Gran <spk121@yahoo.com> 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).
Andy
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: setitimer with Cygwin and Hurd
2017-03-06 21:04 ` Andy Wingo
@ 2017-03-07 14:31 ` Mike Gran
2017-03-07 14:37 ` Andy Wingo
0 siblings, 1 reply; 4+ messages in thread
From: Mike Gran @ 2017-03-07 14:31 UTC (permalink / raw)
To: Andy Wingo; +Cc: Guile-devel Development
>> 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?
-Mike
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: setitimer with Cygwin and Hurd
2017-03-07 14:31 ` Mike Gran
@ 2017-03-07 14:37 ` Andy Wingo
0 siblings, 0 replies; 4+ messages in thread
From: Andy Wingo @ 2017-03-07 14:37 UTC (permalink / raw)
To: Mike Gran; +Cc: Guile-devel Development
On Tue 07 Mar 2017 15:31, Mike Gran <spk121@yahoo.com> 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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-03-07 14:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1493122235.1719816.1488779191346.ref@mail.yahoo.com>
2017-03-06 5:46 ` setitimer with Cygwin and Hurd Mike Gran
2017-03-06 21:04 ` Andy Wingo
2017-03-07 14:31 ` Mike Gran
2017-03-07 14:37 ` Andy Wingo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).