View Single Post
Old 08-16-2012, 11:38 AM   #27
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@knc1: Yeah, that might be a bitch to workaround without using the exact same kernel/glibc pair in the TC, if there's no autoconf check for new or modified args...

I indeed remember it (futex) being a bit messy, but hopefully they took care of assuring a semblance of compatibility in there...

EDIT: Yup, it's the kernel headers. FUTEX_CLOCK_REALTIME isn't implemented in the K3's kernel. So, might be easy enough to fix after all. Just make sure your TC was built against lab126's kernel.

Last edited by NiLuJe; 08-16-2012 at 11:45 AM.
NiLuJe is offline   Reply With Quote