ranlib on MacOS tries to be fancy with ctime/mtime and accidentally truncates them to 1s precision, causing the output file to be older than its inputs. Leading to parallel builds sometimes failing. Thanks, Apple! https://www.postgresql.org/message-id/28417.1543458718%40sss.pgh.pa.us … (and response)
Yes, it would, and that's one more argument in favor of smearing leap seconds until OSes get their shit together and use a monotonic representation of time instead of "approximate number of seconds since 1970".
-
-
But as it turns out leap seconds are fairly rare, running ranlib on APFS happens a few orders of magnitude more often :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Considering your RTC may also be whack and a normal ntp adjustment would introduce a jump backwards, monotonic representations instead of a wall clock time for cases like these would probably be a much better idea anyway. After all we care about order, not specific points in time
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.