From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7172] New: Name collision of rpath token expansion and internal variables
Date: Sun, 8 Jun 2014 02:41:35 +0000 (UTC) [thread overview]
Message-ID: <bug-7172-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7172
Summary: Name collision of rpath token expansion and internal
variables
Product: buildroot
Version: 2014.05
Platform: PC
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: minimod at morethan.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Ref: man ld.so
Example:
In menu -> tool chain -> Target Linker Options (BR2_TARGET_LDFLAGS) to:
-Wl,-rpath='$ORIGIN/../lib'
(A relative path from executable to pathname of its required libraries.
The example in ld.so manual.).
Build BusyBox (which honors BR_TARGET_LDFLAGS, not everything does).
Use: readelf -dl on the resulting binary and find an entry similar to:
0x0000000f (RPATH) Library rpath: [outputRIGIN/../lib]
Where the $O of $ORIGIN has been expanded to an internal value by the time the
content of BR2_TARGET_LDFLAGS is seen by the compiler.
This was when using the Buildroot generation of a toolchain.
Other toolchain selections not tested.
--
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:[~2014-06-08 2:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 2:41 bugzilla at busybox.net [this message]
2014-06-08 7:03 ` [Buildroot] [Bug 7172] Name collision of rpath token expansion and internal variables bugzilla at busybox.net
2014-06-08 10:38 ` Mike Zick
2014-06-08 11:24 ` Samuel Martin
2014-06-08 12:57 ` Mike Zick
2014-06-08 13:53 ` Thomas Petazzoni
2014-06-08 14:04 ` bugzilla at busybox.net
2014-06-08 14:21 ` bugzilla at busybox.net
2014-06-08 15:56 ` bugzilla at busybox.net
2014-06-08 16:03 ` bugzilla at busybox.net
2014-06-08 16:28 ` bugzilla at busybox.net
2014-06-08 16:48 ` bugzilla at busybox.net
2014-06-08 18:18 ` bugzilla at busybox.net
2014-06-08 18:20 ` bugzilla at busybox.net
2014-06-10 12:40 ` bugzilla at busybox.net
2014-06-11 21:36 ` bugzilla at busybox.net
2014-06-22 13:52 ` bugzilla at busybox.net
2014-06-22 13:52 ` bugzilla at busybox.net
2014-06-29 13:14 ` bugzilla at busybox.net
2014-06-29 19:46 ` Mike Zick
2014-07-07 13:06 ` bugzilla at busybox.net
2014-07-17 18:00 ` bugzilla at busybox.net
2014-07-30 20:15 ` bugzilla at busybox.net
2014-07-30 22:41 ` bugzilla at busybox.net
2014-08-01 17:22 ` 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-7172-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