[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080605194732.GB13348@c2.user-mode-linux.org>
Date: Thu, 5 Jun 2008 15:47:32 -0400
From: Jeff Dike <jdike@...toit.com>
To: Nix <nix@...eri.org.uk>
Cc: dhazelton@...er.net, Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
user-mode-linux-devel@...ts.sourceforge.net,
Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [PATCH 1/6] UML - Deal with host time going backwards
On Thu, Jun 05, 2008 at 07:14:30PM +0100, Nix wrote:
> It comes with glibc, and even ls uses it (for clock_gettime(), to
> determine what format to use for date display).
>
> I'd say using it is about as safe as can be.
Without adding -lrt to the link line here (F7), I get
arch/um/os-Linux/built-in.o: In function `nsecs':
/home/jdike/linux/2.6/linux-2.6.22/arch/um/os-Linux/time.c:84: undefined reference to `clock_gettime'
collect2: ld returned 1 exit status
A little odd for a system call...
> Does this really only apply on top of 2.6.22? Which of the bewildering
> blizzard of time-fixup patches we've been exchanging do I need? :)
I have it on top of 2.6.26-rc2-mm1, plus all the other patches I've
sent to Andrew. The patch which started this discussion is the one
you really need though, since this backs it out.
Jeff
--
Work email - jdike at linux dot intel dot com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists