Your message dated Sat, 7 Mar 2015 16:15:30 +0100 with message-id <[email protected]> has caused the report #728213, regarding clock(3) describes that POSIX requires CLOCKS_PER_SEC is 1000000. to be marked as having been forwarded to the upstream software author(s) [email protected]
(NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 728213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728213 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Debian Bug #728213 reported by Tanaka Akira <[email protected]> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728213 Signed-off-by: Stéphane Aulery <[email protected]> --- man3/clock.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man3/clock.3 b/man3/clock.3 index 5787367..3d99b14 100644 --- a/man3/clock.3 +++ b/man3/clock.3 @@ -49,7 +49,7 @@ be represented, the function returns the value .IR (clock_t)\ \-1 . .SH CONFORMING TO C89, C99, POSIX.1-2001. -POSIX requires that +XSI requires that .B CLOCKS_PER_SEC equals 1000000 independent of the actual resolution. -- 2.1.4
--- End Message ---
