From: dgoulet@efficios.com (David Goulet)
Subject: [lttng-dev] Odd dependency for lttng-ust
Date: Mon, 21 Jan 2013 10:53:24 -0500 [thread overview]
Message-ID: <50FD6474.6070207@efficios.com> (raw)
In-Reply-To: <3CA1A65C03C1A34C81BBC6272782E69698788F@valcartierex01.valcartier.drdc-rddc.gc.ca>
Also, I do still forget it still today but after installing URCU and UST:
$ sudo ldconfig
:)
David
Thibault, Daniel:
> -----Message d'origine-----
> De : Mathieu Desnoyers [mailto:mathieu.desnoyers at efficios.com]
> Envoy? : 21 janvier 2013 10:30
>
> No. Distribution packages usually lag behind the project upstream.
> Ubuntu 12.04 has been released last year, and their policy don't allow them to update the packages within this specific distribution version.
>
> This is why you run into trouble when you try to mix distribution packages (from last year) with the current development head.
>
> Don't mix packages from distributions with packages built from sources when version dependencies don't match. All the required dependency information is found in the README files of each project.
>
> Mathieu
> -----Fin du message d'origine-----
>
> But I'm not mixing old packages with new: I tried fetching everything from git.lttng.org. The README for lttng-ust reads in part:
>
> PREREQUISITES:
> - liburcu
> Userspace RCU library, by Mathieu Desnoyers and Paul E. McKenney
> -> This release depends on liburcu v0.7.2
> * Debian/Ubuntu package: liburcu-dev
> * Website: http://lttng.org/urcu
> * Releases: http://lttng.org/files/urcu
> * GitWeb: http://lttng.org/cgi-bin/gitweb.cgi?p=userspace-rcu.git;a=summary
> * Git: git://lttng.org/userspace-rcu.git
>
> Doesn't this say that I can get the required liburcu from git.lttng.org's userspace-rcu? Could it be version 0.7.6 is not retro-compatible with 0.7.2 (that is to say, lttng-ust requires 0.7.2, and 0.7.2 only, not "0.7.2 or later")?
>
> 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
> [Valcartier]\\vsi-wdut-o980, [Secteur-SI]\\edge
> 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/>
> LinkedIn: <http://ca.linkedin.com/in/daniel-u-thibault/>
> Research Gate: <https://www.researchgate.net/profile/Daniel_Thibault/>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2013-01-21 15:53 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
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 [this message]
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=50FD6474.6070207@efficios.com \
--to=dgoulet@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