86 | | #if USE_ABSOLUTE_NANOSLEEP |
---|
| 86 | // If the system time is based on CLOCK_MONOTONIC_RAW we can't use |
---|
| 87 | // TIMER_ABSTIME because wake_at_usec will be in terms of |
---|
| 88 | // CLOCK_MONOTONIC_RAW while clock_nanosleep() can at best use only |
---|
| 89 | // CLOCK_MONOTONIC. There is, AFAIK, no guarantee that the two are even |
---|
| 90 | // remotely related. For now, resolve this problem by unconditionally |
---|
| 91 | // disabling the use of TIMER_ABSTIME here, regardless of the setting of |
---|
| 92 | // USE_ABSOLUTE_NANOSLEEP. Jonathan Woithe, 25 June 2012. |
---|
| 93 | #if USE_ABSOLUTE_NANOSLEEP && 0 |
---|