From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile-devel Development <guile-devel@gnu.org>
Subject: Re: setitimer with Cygwin and Hurd
Date: Mon, 06 Mar 2017 22:04:55 +0100 [thread overview]
Message-ID: <8737eq9kw8.fsf@pobox.com> (raw)
In-Reply-To: <1493122235.1719816.1488779191346@mail.yahoo.com> (Mike Gran's message of "Mon, 6 Mar 2017 05:46:31 +0000 (UTC)")
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
next prev parent reply other threads:[~2017-03-06 21:04 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 [this message]
2017-03-07 14:31 ` Mike Gran
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=8737eq9kw8.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.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).