[fedora-arm] Fwd: Does clock_gettime support CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM?

Dan Horák dan at danny.cz
Tue Oct 15 06:26:21 UTC 2013


forwarding a message from our Ruby maintainer asking for help

looks like a kernel problem, please see also
https://bugs.ruby-lang.org/issues/9008#note-3


		Dan

-------- Původní zpráva --------
Předmět: 	Does clock_gettime support CLOCK_REALTIME_ALARM and 
CLOCK_BOOTTIME_ALARM?
Datum: 	Thu, 10 Oct 2013 13:48:01 +0200
Od: 	Vít Ondruch <vondruch at redhat.com>
Komu: 	arm at lists.fedoraproject.org



Hi,

I am trying to build Ruby 2.1 for F21 and I observe following test
errors:

   3) Error:
TestProcess#test_clock_getres_constants:
Errno::E524: Unknown error 524 - clock_getres
     /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
`clock_getres' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1752:in
`block in
test_clock_getres_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
`each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1749:in
`test_clock_getres_constants'
   4) Error:
TestProcess#test_clock_gettime_constants:
Errno::E524: Unknown error 524 - clock_gettime
     /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
`clock_gettime' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1676:in
`block in
test_clock_gettime_constants' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
`each' /builddir/build/BUILD/ruby-2.1.0-preview1/test/ruby/test_process.rb:1673:in
`test_clock_gettime_constants'


It looks like CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM are not
supported, but the error code is completely strange to me. According to
the documentation, it should return EINVAL.

http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_getres.html
  |
  | [EINVAL]
  | The clock_id argument does not specify a known clock.

Any help is appreciated.

Thanks



Vít




P.S. This is my upstream report: http://bugs.ruby-lang.org/issues/9008
P.S.2 I am not subscribed to this list, please keep me in the CC.





More information about the arm mailing list