Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] Odd dependency for lttng-ust
Date: Mon, 21 Jan 2013 09:59:54 -0500	[thread overview]
Message-ID: <20130121145954.GA1472@Krystal> (raw)
In-Reply-To: <3CA1A65C03C1A34C81BBC6272782E696987880@valcartierex01.valcartier.drdc-rddc.gc.ca>

* Thibault, Daniel (Daniel.Thibault at drdc-rddc.gc.ca) wrote:
> I'm starting from a clean Ubuntu 12.04 installation after adding the various prerequisites of the git.lttng.org LTTng 2 packages:
> 
> LTTng 2 Packages (in the proper dependency order):
> 
> lttng-modules (2.1.0+-c6403de)
> userspace-rcu (0.7.6-da9bed2)
> lttng-ust (2.1.0+-340f776)
> lttng-tools (2.1.1+-281047b)
> 
> Prerequisites installed:
> 
> automake
> binutils-gold
> bison
> flex
> libpopt-dev
> libtool
> libuuid1
> python-dev
> swig2.0
> kernel's headers (i.e. linux-headers-generic)
> texinfo
> g++
> 
> After making and installing lttng-modules and userspace-rcu successfully, lttng-ust's configure fails with:
> 
> checking for _cds_lfht_new in -lurcu-cds... no
> configure: error: Cannot find
> liburcu-cds lib, part of Userspace RCU 0.7 or better.
> 
> This occurs even though userspace-rcu installed
> /usr/local/lib/liburcu-cds.  It seems I must install liburcu-dev from
> the LTTng PPA (because the current Ubuntu liburcu-dev is 0.6.7 while
> lttng-ust requires 0.7 or better) before I can configure lttng-ust
> properly.  This is a weird bootstrapping problem: could the
> userspace-rcu package's install be incomplete?

Quoting the lttng-tools README file:

"    - liburcu
      Userspace RCU library, by Mathieu Desnoyers and Paul E. McKenney

      -> Tested with liburcu >= v0.7.2"

Therefore you need to install Userspace RCU 0.7.2 or later.

A dependency is not only on a package, but also on a range of versions.

Thanks,

Mathieu


> 
> Daniel U. Thibault
> R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) / Defence R&D Canada - Valcartier (DRDC Valcartier)
> Cyber s?curit? pour les missions essentielles (CME) / Mission Critical Cyber Security (MCCS)
> Protection des syst?mes et contremesures (PSC) / Systems Protection & Countermeasures (SPC)
> 2459 route de la Bravoure
> Qu?bec, QC? G3J 1X5
> CANADA
> Vox?: (418) 844-4000 x4245
> Fax?: (418) 844-4538
> NAC?: 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
> Gouvernement du Canada?/ Government of Canada
> <http://www.valcartier.drdc-rddc.gc.ca/>
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com



  reply	other threads:[~2013-01-21 14:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 14:52 Thibault, Daniel
2013-01-21 14:59 ` Mathieu Desnoyers [this message]
2013-01-21 15:24   ` Thibault, Daniel
2013-01-21 15:29     ` Mathieu Desnoyers
2013-01-21 15:44       ` Thibault, Daniel
2013-01-21 15:47         ` Mathieu Desnoyers
2013-01-21 15:53         ` David Goulet
2013-01-21 16:50           ` Thibault, Daniel
2013-01-21 17:06             ` Mathieu Desnoyers
2013-01-21 17:31               ` Thibault, Daniel
2013-01-21 18:38                 ` Mathieu Desnoyers
2013-01-21 19:34                   ` Thibault, Daniel
2013-01-21 20:06                     ` Christian Babeux

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=20130121145954.GA1472@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