From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8316] New: lttng-tools and lttng-babeltrace executables contain bad RPATH pointing to host machine
Date: Thu, 27 Aug 2015 16:29:29 +0000 (UTC) [thread overview]
Message-ID: <bug-8316-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8316
Summary: lttng-tools and lttng-babeltrace executables contain
bad RPATH pointing to host machine
Product: buildroot
Version: 2015.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: benjamin.h.shelton at intel.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
The lttng-tools and lttng-babeltrace executables contain bad RPATHs pointing to
the buildroot output/build directory. This happens with lttng-tools versions
2.6.0 and 2.7.0-rc1, as well as with lttng-babeltrace.
objdump -p shows the following:
RPATH
/workspace/sw/bhshelto/buildroot/buildroot/output/build/lttng-tools-2.7.0-rc1/src/lib/lttng-ctl/.libs:/workspace/sw/bhshelto/buildroot/buildroot/output/host/usr/aarch64-buildroot-linux-gnu/sysroot/usr/lib:/workspace/sw/bhshelto/buildroot/buildroot/output/build/liburcu-0.8.7/.libs
This is a problem for us because /workspace is an NFS mount that we use for
development builds, and we also mount it on our embedded targets. When
/workspace is not mounted on the embedded target, the lttng utilities run fine,
since the RPATH does not match anything. However, if I mount /workspace, I see
the following:
[root at buildroot cli]# lttng stop
lttng: error while loading shared libraries:
/workspace/sw/bhshelto/buildroot/buildroot/output/build/lttng-tools-2.7.0-rc1/src/lib/lttng-ctl/.libs/liblttng-ctl.so.0:
file too short
[root at buildroot cli]# cd
[root at buildroot ~]# umount /workspace
[root at buildroot ~]# lttng stop
Waiting for data availability
Tracing stopped for session my-session
When I use patchelf to remove the RPATH, everything works as expected.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2015-08-27 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 16:29 bugzilla at busybox.net [this message]
2015-08-27 18:09 ` [Buildroot] [Bug 8316] lttng-tools and lttng-babeltrace executables contain bad RPATH pointing to host machine bugzilla at busybox.net
2015-10-14 9:41 ` bugzilla at busybox.net
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=bug-8316-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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