From: christian.babeux@efficios.com (Christian Babeux)
Subject: [lttng-dev] Odd dependency for lttng-ust - resolved
Date: Fri, 25 Jan 2013 13:48:28 -0500 [thread overview]
Message-ID: <CAGDH53nScT2=KHr=P_tdDA-rSAnNvfga0V9Q_K4aA3JD06Shpg@mail.gmail.com> (raw)
In-Reply-To: <3CA1A65C03C1A34C81BBC6272782E696987A7F@valcartierex01.valcartier.drdc-rddc.gc.ca>
> Nope, my /usr/lib is clean. The problem is unavoidable on a clean system because lttng-tools's README lists GNU Gold (2.22 or better) in its requirements when building from git. On the other hand, if you had a liburcu package installed and it were not too old, configure's checks would be passed. You could run into trouble during the make though, depending on which liburcu (/usr/lib vs. /usr/local/lib) it linked against. But that scenario is moot as Mathieu rightly warned against mixing old and new stuff together.
The README has been clarified in commit
ee10cdeb41ab238ebdc9ae3d1b2a4dbbe930df9b.
The bottom line is:
With GNU ld: ./configure *should* work as is if "/usr/local/lib" is
correctly specified in /etc/ld.so.conf. Note that this is
_distribution specific_ and you might have to use
LDFLAGS=-L/usr/local/lib ./configure on other distros.
With GNU Gold: Use LDFLAGS=-L/usr/local/lib ./configure if
dependencies have been installed in /usr/local/*.
Thanks,
Christian
prev parent reply other threads:[~2013-01-25 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 17:32 Thibault, Daniel
2013-01-25 17:57 ` Alexandre Montplaisir
2013-01-25 18:26 ` Thibault, Daniel
2013-01-25 18:48 ` Christian Babeux [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='CAGDH53nScT2=KHr=P_tdDA-rSAnNvfga0V9Q_K4aA3JD06Shpg@mail.gmail.com' \
--to=christian.babeux@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