qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Roger Pau Monne <roger.pau@entel.upc.edu>
Cc: qemu-devel@nongnu.org, xen-devel@lists.xen.org
Subject: Re: [Qemu-devel] [PATCH 2/2] build: replace librt check function
Date: Wed, 22 Feb 2012 13:25:58 -0600	[thread overview]
Message-ID: <4F454146.1050007@codemonkey.ws> (raw)
In-Reply-To: <1329739880-18752-2-git-send-email-roger.pau@entel.upc.edu>

On 02/20/2012 06:11 AM, Roger Pau Monne wrote:
> Replace clock_gettime with timer_gettime, since at least under
> uclibc 0.9.33 the clock_getttime function can be used without linking
> against librt (although the manual page states the opposite).
>
> Signed-off-by: Roger Pau Monne<roger.pau@entel.upc.edu>

I don't think this is against qemu.git.  Please do not send patches to 
qemu-devel that are not against qemu.git without clearly indicating this.

Regards,

Anthony Liguori

> ---
>   configure |    3 ++-
>   1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/configure b/configure
> index 7bcd547..fb99632 100755
> --- a/configure
> +++ b/configure
> @@ -2438,7 +2438,8 @@ fi
>   cat>  $TMPC<<EOF
>   #include<signal.h>
>   #include<time.h>
> -int main(void) { clockid_t id; return clock_gettime(id, NULL); }
> +int main(void) { timer_t tid; struct itimerspec it; \
> +                 return timer_gettime(tid,&it); }
>   EOF
>
>   if compile_prog "" "" ; then

  reply	other threads:[~2012-02-22 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 12:11 [Qemu-devel] [PATCH 1/2] build: check if libm is needed in configure Roger Pau Monne
2012-02-20 12:11 ` [Qemu-devel] [PATCH 2/2] build: replace librt check function Roger Pau Monne
2012-02-22 19:25   ` Anthony Liguori [this message]
2012-02-23 13:34     ` Roger Pau Monné
2012-02-27  9:52       ` [Qemu-devel] [Xen-devel] " Ian Campbell
2012-02-27 10:07         ` Roger Pau Monné
2012-02-27 12:49         ` Stefano Stabellini

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=4F454146.1050007@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=roger.pau@entel.upc.edu \
    --cc=xen-devel@lists.xen.org \
    /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;
as well as URLs for NNTP newsgroup(s).