Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

glibc 2.9 "make check" fails on rt/tst-cputimer with "timer sig[12] invoked to soon"

13 views
Skip to first unread message

shac...@gmail.com

unread,
Feb 13, 2009, 5:55:12 AM2/13/09
to
I wish to install a new libc.so and have compiled the latest
glibc (2.9.90) with the latest gcc (4.3.3) and the latest
binutils (2.19, compiled with gcc 4.3.3). Compilation
succeeded without errors, although not before I did some non-
obvious things (e.g., I had to put '-march=i686' into my
CFLAGS to avoid getting undefined symbol errors from the
linker). 'Make check' also produced errors, a number of which
I averted by doing non-obvious things (e.g., I had to copy
iconvdata/gconv-modules and libio/tst-*.input from the source
directory to the build directory, and I had to export into the
environment TIMEOUTFACTOR=2; the glibc documentation gave me
no clue that I had to do any of those things). Now I am
running into an error with rt/tst-cputimer that I do not know
how to avert. I have run 'make check' 3 times; here are the
3 results. From rt/tst-cputimer1.out:

clock_gettime returned timespec = { 0, 8000000 }
clock_getres returned timespec = { 0, 1 }
*** timer sig1 invoked too soon: 2.908000000 instead of expected
3.408000000
*** timer sig2 invoked too soon: 2.908000000 instead of expected
3.908000000

And from rt/tst-cputimer2.out:

clock_gettime returned timespec = { 0, 0 }
clock_getres returned timespec = { 0, 1 }
*** timer sig1 invoked too soon: 2.900000000 instead of expected
3.400000000
*** timer sig2 invoked too soon: 2.900000000 instead of expected
3.900000000

Before running the 3rd 'make check', I increased TIMEOUTFACTOR
(to 3). It made no difference. From rt/tst-cputimer3.out:

clock_gettime returned timespec = { 0, 0 }
clock_getres returned timespec = { 0, 1 }
*** timer sig1 invoked too soon: 2.900000000 instead of expected
3.400000000
*** timer sig2 invoked too soon: 2.900000000 instead of expected
3.900000000


I don't want to install the new libc.so until I can get all the
tests to succeed, or, failing that, until I understand the
significance of the error, and can intelligently dismiss it.
What shall I do? Thank you in advance for your replies.


Jay F. Shachter
6424 North Whipple Street
Chicago IL 60645-4111
(1-773) 7613784
j...@m5.chicago.il.us
http://m5.chicago.il.us

0 new messages