All of lore.kernel.org
 help / color / mirror / Atom feed
From: Natanael Copa <natanael.copa@gmail.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu/configure: correctly detect -lrt ldflag on uclibc
Date: Thu, 29 Jan 2009 11:42:09 +0100	[thread overview]
Message-ID: <1233225729.9550.28.camel@nc> (raw)
In-Reply-To: <4970DB88.4070902@codemonkey.ws>

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

On Fri, 2009-01-16 at 13:10 -0600, Anthony Liguori wrote:
> Natanael Copa wrote:
> > Hi,
> >
> > I managed to build kvm on/for my uclibc distro, Alpine linux. The qemu
> > configure script failed to detect if it needed the -lrt ldflag. the
> > attatched patch fixes the test.
> >
> > Thanks!
> >
> > -nc
> >
> > PS. please CC me as i don't subscribe to the list.
> >   
> Please submit this against QEMU SVN, not against a release of KVM.

I created a new patch for your convenience agains current trunk. (even
if the previous patch appled just fine with -p2)

Thanks!

-nc

[-- Attachment #2: qemu-r6469-uclibc.patch --]
[-- Type: text/x-patch, Size: 411 bytes --]

Index: configure
===================================================================
--- configure	(revision 6469)
+++ configure	(working copy)
@@ -1059,7 +1059,10 @@
 cat > $TMPC <<EOF
 #include <signal.h>
 #include <time.h>
-int main(void) { clockid_t id; return clock_gettime(id, NULL); }
+int main(void) { clockid_t id; timer_t tid;
+	return clock_gettime(id, NULL) + timer_delete(tid); 
+}
+
 EOF
 
 rt=no

  reply	other threads:[~2009-01-29 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  6:54 [Qemu-devel] [PATCH] qemu/configure: correctly detect -lrt ldflag on uclibc Natanael Copa
2009-01-16 19:10 ` Anthony Liguori
2009-01-29 10:42   ` Natanael Copa [this message]
2009-01-29 13:36     ` Anthony Liguori

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=1233225729.9550.28.camel@nc \
    --to=natanael.copa@gmail.com \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.