* bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
@ 2016-06-29 12:53 Rahul AG
2017-03-01 8:10 ` Andy Wingo
2017-03-01 8:11 ` Andy Wingo
0 siblings, 2 replies; 3+ messages in thread
From: Rahul AG @ 2016-06-29 12:53 UTC (permalink / raw)
To: 23870
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
2016-06-29 12:53 bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra Rahul AG
@ 2017-03-01 8:10 ` Andy Wingo
2017-03-01 8:11 ` Andy Wingo
1 sibling, 0 replies; 3+ messages in thread
From: Andy Wingo @ 2017-03-01 8:10 UTC (permalink / raw)
To: Rahul AG; +Cc: 23870
On Wed 29 Jun 2016 14:53, Rahul AG <r@hul.ag> writes:
> 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.
Hi, this is fixed in 2.1.7 and now also in 2.0 git. I guess a
subsequent 2.0.15 will include this fix. Thanks for the report.
Andy
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
2016-06-29 12:53 bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra Rahul AG
2017-03-01 8:10 ` Andy Wingo
@ 2017-03-01 8:11 ` Andy Wingo
1 sibling, 0 replies; 3+ messages in thread
From: Andy Wingo @ 2017-03-01 8:11 UTC (permalink / raw)
To: 23870-done
close
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-03-01 8:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-29 12:53 bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra Rahul AG
2017-03-01 8:10 ` Andy Wingo
2017-03-01 8:11 ` 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).