Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jan.glauber@gmail.com (Jan Glauber)
Subject: [lttng-dev] lttng-tools liburcu path
Date: Thu, 27 Mar 2014 13:25:25 +0100	[thread overview]
Message-ID: <20140327122524.GB29197@hal> (raw)
In-Reply-To: <20140327103453.GA29197@hal>

With this patch it works for me, but I'm no autoconf wizard and I just realized
I also could use:

./configure  --disable-lttng-ust --with-lttng-ust-prefix=/usr/local/

to make it work since all I need is the additional -L path...

--Jan

diff --git a/configure.ac b/configure.ac
index 54f82cf..59e8344 100644
--- a/configure.ac
+++ b/configure.ac
@@ -200,6 +200,15 @@ AC_CHECK_DECL([cmm_smp_mb__before_uatomic_or], [],
         [AC_MSG_ERROR([liburcu $liburcu_version or newer is needed])], [[#include <urcu.h>]]
 )
 
+AC_ARG_WITH(liburcu-prefix,
+  AS_HELP_STRING([--with-liburcu-prefix=PATH],
+                 [Specify the installation prefix of the liburcu library.
+	          Headers must be in PATH/include; libraries in PATH/lib.]),
+		  [
+		    CPPFLAGS="$CPPFLAGS -I${withval}/include"
+		    LDFLAGS="$LDFLAGS -L${withval}/lib64 -L${withval}/lib"
+		  ])
+
 AC_ARG_WITH(lttng-ust-prefix,
   AS_HELP_STRING([--with-lttng-ust-prefix=PATH],
                  [Specify the installation prefix of the lttng-ust library.

On Thu, Mar 27, 2014 at 11:34:54AM +0100, Jan Glauber wrote:
> Hi David,
> 
> I'm getting linker errors for lttng-tools, due to an older version of
> liburcu (<0.7) installed. Now I was looking for a configure switch to
> specify where the liburcu that should be used is but I didn't find one.
> 
> Would it be possible to add something like --with-xml-prefix= but for
> luburcu?
> 
> thanks, Jan



      reply	other threads:[~2014-03-27 12:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 10:34 Jan Glauber
2014-03-27 12:25 ` Jan Glauber [this message]

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=20140327122524.GB29197@hal \
    --to=jan.glauber@gmail.com \
    /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