From James Cowgill@21:1/5 to Debian Bug Tracking System on Fri Aug 18 16:40:03 2017
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MBX9jjCPr00gB4fAtOarn4q9SvwxXXcku
This is a multi-part message in MIME format. --------------6649FC4CFDE1DCE53E020711
Content-Type: text/plain; charset=utf-8
Control: affects -1 src:ffmpeg
The clock() function on hurd has the wrong scaling factor. It generates
only 100 clock ticks per second, even though CLOCKS_PER_SEC is 1000000.
I has written a small testcase (attached) which illustrates the difference:
While I appreciate that hurd's clock may not be able to be as precise as
on Linux, but it should still return values which corresponds in some
way to CLOCKS_PER_SEC.
As far as I can tell, this bug is caused by the Debian patch: debian/patches/hurd-i386/unsubmitted-clock_t_centiseconds.diff
The patch header contains a description about applications failing with
high precision. IMHO those applications are broken. Their bugs should
not be worked around in libc and that patch should be dropped.
This was originally found after debugging ffmpeg. I believe the FTBFS on
hurd is caused by this bug.