Katze

As you just mentioned in #43, there is the possibility of a custom callback. Is this callback replacing the original handler? Because if it is, then I see no clean...

So, you are planning to have the system interrupt triggered by the RTC to count up a 64-bit integer and have the gettimeofday (and possible other functions) return an accurate...

Then you could have some memory location (which is by default initialized to 0) which is used by all time functions to save the hardware time to (on first access...

Preferably you could write one function (similar to `time(0)`) which just returns the result of the addition, which then is used in all others. No need to repeat yourself then.

If you update the hardware time with this setup, you would just have to overwrite that memorylocation where the hardwaretime is saved in the firstplace with 0. Then all time...

Please note that this would assume that the RTC interrupt only happens once per second, if an application needs a different interval and wants to use the RTC for that,...

To bring in a specific use case; some (most?) *crond* implementations support the use of `EAGAIN` as an exit code to trigger a retry. I am currently running into an...

The setup that I have in place currently, but looking to possibly replace with lego for the sake of using tools that automate this task, is built on the principle...

Same problem on Gentoo. Proposed fix/workaround by @BenBE works. ``` gcc (Gentoo 7.3.0-r3 p1.4) 7.3.0 ```

Alternatively you can also use `-no-pie`. The PIE-change was introduced in Gentoo with profile 17.0, the [news](https://www.gentoo.org/support/news-items/2017-11-30-new-17-profiles.html) for that change contain the following on the matter: ``` 2) Where supported,...