linux-um archives
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Jeff Dike <jdike@addtoit.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net, dhazelton@enter.net
Subject: Re: [uml-devel] [PATCH 1/6] UML - Deal with host time going backwards
Date: Thu, 05 Jun 2008 22:41:55 +0100	[thread overview]
Message-ID: <87bq2f8spo.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20080605194732.GB13348@c2.user-mode-linux.org> (Jeff Dike's message of "Thu, 5 Jun 2008 15:47:32 -0400")

On 5 Jun 2008, Jeff Dike uttered the following:

> 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

Yes, you'll definitely *need* -lrt for clock_*().

> 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...

I think it's in there because it's part of the POSIX realtime
extensions, so you should have to, as it were, assent to using something
that's not as portable as just using libc. It makes more sense than
libm, anyway.

(It's completely moot for UML of course :) )

-- 
`If you are having a "ua luea luea le ua le" kind of day, I can only
 assume that you are doing no work due [to] incapacitating nausea caused 
 by numerous lazy demons.' --- Frossie

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2008-06-05 21:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 19:02 [uml-devel] [PATCH 1/6] UML - Deal with host time going backwards Jeff Dike
2008-06-03 19:32 ` Andrew Morton
2008-06-03 19:43   ` Daniel Hazelton
2008-06-03 19:52     ` Nix
2008-06-03 20:07       ` Andrew Morton
2008-06-03 20:37         ` Daniel Hazelton
2008-06-03 21:00         ` Jeff Dike
2008-06-04  1:50           ` Eric W. Biederman
2008-06-04  3:15             ` Jeff Dike
2008-06-04  5:12             ` Daniel Hazelton
2008-06-04 14:31           ` Jeremy Fitzhardinge
2008-06-04 19:37             ` Jeff Dike
2008-06-04 20:05               ` Jeremy Fitzhardinge
2008-06-05 15:30                 ` Jeff Dike
2008-06-05 18:14                   ` Nix
2008-06-05 19:47                     ` Jeff Dike
2008-06-05 21:41                       ` Nix [this message]
2008-06-05 18:19                   ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2008-06-03 19:59 devzero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bq2f8spo.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=dhazelton@enter.net \
    --cc=jdike@addtoit.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox