[debbugs-tracker] bug#23870: closed (Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra)

[GNU bug Tracking System]

Your message dated Wed, 01 Mar 2017 09:11:16 +0100
with message-id <address@hidden>
and subject line Re: bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on 
macOS 10.12 Sierra
has caused the debbugs.gnu.org bug report #23870,
regarding Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
23870: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23870
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
>
>
>
>
> Date: 
>
> Wed, 29 Jun 2016 20:53:55 +0800
>
>
>
>
> 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
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#23870: Guile 2.0.11 can't find clock_getcpuclockid on macOS 10.12 Sierra
>
>
>
>
> Date: 
>
> Wed, 01 Mar 2017 09:11:16 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
>
>
>
>
> close
>
>
> --- End Message ---