diff options
| author | Roy Marples <roy@marples.name> | 2008-08-01 08:41:25 +0000 |
|---|---|---|
| committer | Roy Marples <roy@marples.name> | 2008-08-01 08:41:25 +0000 |
| commit | 8fd2efb43e5d216dadd6386d7e26663b22f2144f (patch) | |
| tree | 09c00162d9542bf21e154cbe7ea504c23715c360 /README | |
| parent | f92a185f0ef10af23a273c225a793a6d3c6a4a6e (diff) | |
| download | dhcpcd-8fd2efb43e5d216dadd6386d7e26663b22f2144f.tar.xz | |
Tweak README about monotonic, and improve warning message.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -15,12 +15,15 @@ If you're cross compiling you may need to set the below knobs to avoid automatic tests. OS=BSD | Linux -If you're building for a NOMMU system where fork() does not work, you should -add -DTHERE_IS_NO_FORK to your CPPFLAGS. +If you're building for an MMU-less system where fork() does not work, you +should add -DTHERE_IS_NO_FORK to your CPPFLAGS. dhcpcd will try and use a monotonic clock when possible. Some libc implementations do not correctly report that they have a monotonic clock, but they have the headers to make it work. dhcpcd will warn about this. +Without a monotonic clock, we fall victim of the year 2038 time_t bug on +32-bit platforms AND the timers will be sufer from clock skew if the system +clock changes. To force the use of a monotonic clock you can add -DFORCE_MONOTONIC to your CPPFLAGS. |