From mboxrd@z Thu Jan 1 00:00:00 1970 From: christian.babeux@efficios.com (Christian Babeux) Date: Fri, 25 Jan 2013 13:48:28 -0500 Subject: [lttng-dev] Odd dependency for lttng-ust - resolved In-Reply-To: <3CA1A65C03C1A34C81BBC6272782E696987A7F@valcartierex01.valcartier.drdc-rddc.gc.ca> References: <3CA1A65C03C1A34C81BBC6272782E696987A76@valcartierex01.valcartier.drdc-rddc.gc.ca> <5102C77A.5040409@voxpopuli.im> <3CA1A65C03C1A34C81BBC6272782E696987A7F@valcartierex01.valcartier.drdc-rddc.gc.ca> Message-ID: > 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