From: Mike Gran <spk121@yahoo.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile-devel Development <guile-devel@gnu.org>
Subject: Re: setitimer with Cygwin and Hurd
Date: Tue, 7 Mar 2017 14:31:16 +0000 (UTC) [thread overview]
Message-ID: <1079723129.393127.1488897076118@mail.yahoo.com> (raw)
In-Reply-To: <8737eq9kw8.fsf@pobox.com>
>> 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
next prev parent reply other threads:[~2017-03-07 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2017-03-07 14:37 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1079723129.393127.1488897076118@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).