From: Rahul AG <r@hul.ag>
To: 23870@debbugs.gnu.org
Subject: bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
Date: Wed, 29 Jun 2016 20:53:55 +0800 [thread overview]
Message-ID: <1E4CE00A-AC4E-4D1F-94C7-12C71C0B838A@hul.ag> (raw)
Guile version: 2.0.11
Machine type: x86_64-apple-darwin16.0.0
macOS 10.12 introduces the `clock_gettime` family of functions, with slight differences from the *BSD and Linux implementations.
The failure in linking is caused by a call at libguile/stime.c @ L841 to `clock_getcpuclockid`, which does NOT exist on macOS, while `_POSIX_CPUTIME` and `CLOCK_PROCESS_CPUTIME_ID` do exist.
I have an absolutely hideous patch[1] locally applied that gets things compiling (and get-internal-run-time seems to work), but is otherwise terrible from a readability and maintainability standpoint. That said, narrowing it down to that single call should help make this fix easier.
Cheers.
Rahul
[1] https://gist.github.com/rahulg/baa500e84136f0965e9ade2fb36b90ba
next reply other threads:[~2016-06-29 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 12:53 Rahul AG [this message]
2017-03-01 8:10 ` bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra Andy Wingo
2017-03-01 8:11 ` 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=1E4CE00A-AC4E-4D1F-94C7-12C71C0B838A@hul.ag \
--to=r@hul.ag \
--cc=23870@debbugs.gnu.org \
/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).