qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mohamad Gebai <mohamad.gebai@gmail.com>
To: qemu-devel@nongnu.org
Cc: Mohamad Gebai <mohamad.gebai@polymtl.ca>
Subject: [Qemu-devel] [RFC PATCH 1/3] Fix configure script for LTTng 2.x
Date: Mon, 30 Sep 2013 11:04:59 -0400	[thread overview]
Message-ID: <1380553501-20670-2-git-send-email-mohamad.gebai@polymtl.ca> (raw)
In-Reply-To: <1380553501-20670-1-git-send-email-mohamad.gebai@polymtl.ca>

Signed-off-by: Mohamad Gebai <mohamad.gebai@polymtl.ca>
---
 configure |    9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/configure b/configure
index 05e16da..b3c9b80 100755
--- a/configure
+++ b/configure
@@ -3283,15 +3283,14 @@ fi
 # For 'ust' backend, test if ust headers are present
 if test "$trace_backend" = "ust"; then
   cat > $TMPC << EOF
-#include <ust/tracepoint.h>
-#include <ust/marker.h>
+#include <lttng/tracepoint.h>
 int main(void) { return 0; }
 EOF
   if compile_prog "" "" ; then
-    LIBS="-lust -lurcu-bp $LIBS"
-    libs_qga="-lust -lurcu-bp $libs_qga"
+    LIBS="-llttng-ust -lurcu-bp -ldl $LIBS"
+    libs_qga="-llttng-ust -lurcu-bp -ldl $libs_qga"
   else
-    error_exit "Trace backend 'ust' missing libust header files"
+    error_exit "Trace backend 'ust' missing lttng-ust header files"
   fi
 fi
 
-- 
1.7.10.4

  reply	other threads:[~2013-09-30 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 15:04 [Qemu-devel] [RFC PATCH 0/3] Fix UST backend for LTTng 2.x Mohamad Gebai
2013-09-30 15:04 ` Mohamad Gebai [this message]
2013-09-30 15:05 ` [Qemu-devel] [RFC PATCH 2/3] Modified the tracetool framework " Mohamad Gebai
2013-09-30 15:05 ` [Qemu-devel] [RFC PATCH 3/3] Adapt Makefiles to the new LTTng ust interface Mohamad Gebai
2013-10-01 10:04 ` [Qemu-devel] [RFC PATCH 0/3] Fix UST backend for LTTng 2.x Alex Bennée

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=1380553501-20670-2-git-send-email-mohamad.gebai@polymtl.ca \
    --to=mohamad.gebai@gmail.com \
    --cc=mohamad.gebai@polymtl.ca \
    --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 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).