Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] pkg-config --libs does not include -lurcu-bp
Date: Tue, 3 Apr 2012 08:51:50 -0400	[thread overview]
Message-ID: <20120403125150.GA14534@Krystal> (raw)
In-Reply-To: <CAJSP0QX5oFByhHNw6=UPEKkw2mTmznHxn_xUFy+sOjDcQwqSOA@mail.gmail.com>

Hi Stefan,

I think Debian did not switch to LTTng 2.0 yet, am I correct ? It would
be good to do the switch pretty soon, as 0.x is being less and less
supported. All the packages have been created and integrated into the
Ubuntu 12.04 LTS universe.

I remember we ensured, in UST 0.x, that the libust.so is itself linked
against liburcu-bp, so the latter does not need to be explicitely
specified on the compiler/linker command line. I would recommend to
gradually deprecate the 0.x toolchain in favor of 2.0 though.

Thanks,

Mathieu

* Stefan Hajnoczi (stefanha at gmail.com) wrote:
> It's necessary to link against -lurcu-bp when using LTTng UST but on
> Debian testing with libust-dev 0.16-1 I get the following from
> pkg-config:
> 
> $ pkg-config --libs ust
> -lust
> 
> I see /ust/lib/pkgconfig/ust.pc already contains Requires.private:
> liburcu-bp but that isn't reflected in the --libs output.  Does it
> need to be updated?
> 
> Thanks,
> Stefan
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com



  parent reply	other threads:[~2012-04-03 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  8:45 Stefan Hajnoczi
2012-04-03 12:47 ` Yannick Brosseau
2012-04-03 12:51 ` Mathieu Desnoyers [this message]
2012-04-03 20:59   ` Jon Bernard

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=20120403125150.GA14534@Krystal \
    --to=mathieu.desnoyers@efficios.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