From: naruse@... Date: 2016-10-06T03:44:06+00:00 Subject: [ruby-core:77498] [Ruby trunk Bug#12808][Closed] Ruby builds do not produce Process::UPTIME constant on macOS Sierra Issue #12808 has been updated by Yui NARUSE. Status changed from Open to Closed It will be an Ruby 2.4 feature by r56200. ---------------------------------------- Bug #12808: Ruby builds do not produce Process::UPTIME constant on macOS Sierra https://bugs.ruby-lang.org/issues/12808#change-60764 * Author: Andrew Smith * Status: Closed * Priority: Normal * Assignee: * ruby -v: ruby 2.1.9p490 (2016-03-30 revision 54437) [x86_64-darwin16] * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- Due to the fact that macOS Sierra does not define CLOCK_UPTIME in /usr/include/time.h the UPTIME constant is never generated during the Ruby build. macOS defines CLOCK_UPTIME_RAW instead as.. clock that increments monotonically, in the same manner as CLOCK_MONOTONIC_RAW, but that does not increment while the system is asleep. The returned value is identical to the result of mach_absolute_time() after the appropriate mach_timebase conversion is applied. It appears this is done to provide a selection for uptime value based on sleeping or non sleeping return value. -- https://bugs.ruby-lang.org/ Unsubscribe: