http://bugzilla.opensuse.org/show_bug.cgi?id=936251
http://bugzilla.opensuse.org/show_bug.cgi?id=936251#c2
--- Comment #2 from Anton Samsonov
This is easy to work around by defining it yourself.
As obvious as it may seem, as ugly and non-portable quirk it would be, because both symbolic names and numeric values differ across platforms. For example, the very same value 11 that is used to represent CLOCK_TAI in Linux (although I would not bet for custom hardware-specific distros), means CLOCK_MONOTONIC_PRECISE in FreeBSD. Similarly, CLOCK_REALTIME is usually represented by value 0, but not in Cygwin, where it equals 1. (An overview of these disagreements can be seen at http://stackoverflow.com/q/31073923) In general, I did not see a system which explicitly documented numeric values for CLOCK_xxx, so any manual definition would be a bold guess. -- You are receiving this mail because: You are on the CC list for the bug.