Micah Cowan <[EMAIL PROTECTED]> writes: >> 2) When I download files from a URL I get the following error: >> >> Cannot get REALTIME clock frequency: Invalid argument > > I can't tell you why that'd happen; Wget falls back to a clock id that > should be guaranteed to exist. An erroneous time.h header would perhaps > explain it. > > The error isn't serious, though, and may safely be ignored. > > In fact: Hrvoje? What do you think about removing that warning > altogether (or, perhaps, increasing the verbosity level required to > issue it)? AFAICT, the clock's resolution is used in only one place,
I agree that clock_getres itself isn't important. Still, Wget needs to choose a clock that actually works out of several possible clocks allowed by POSIX (and common extensions), so it's advisable to at least attempt to use the clock in some way. If clock_getres is known to fail on some platforms, then we should use clock_gettime instead. I wonder if clock_gettime works for a clock for which clock_getres fails.
