From: Wolfgang Grandegger <wg@grandegger.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 2/9] support/scripts: add fix-rpath script to sanitize the rpath
Date: Fri, 3 Mar 2017 17:39:42 +0100 [thread overview]
Message-ID: <c8a4d85e-ff1a-44ab-832b-bd4eff235a00@grandegger.com> (raw)
In-Reply-To: <20170303154853.4eb15819@free-electrons.com>
Hello,
Am 03.03.2017 um 15:48 schrieb Thomas Petazzoni:
> Hello,
>
> On Fri, 3 Mar 2017 15:18:46 +0100, Wolfgang Grandegger wrote:
>> From: Samuel Martin <s.martin49@gmail.com>
>>
>> This commit introduces a fix-rpath script able to scan a tree,
>> detect ELF files, check their RPATH and fix it in a proper way.
>> The RPATH fixup is done by the patchelf utility using the option
>> "--make-rpath-relative".
>>
>> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
>> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com>
>> ---
>> support/scripts/fix-rpath | 106 ++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 106 insertions(+)
>> create mode 100755 support/scripts/fix-rpath
>
> Now that patchelf is much smarter, I am wondering if we still really
> need a utility script just to call patchelf. Have you tried bringing
> this logic into the make logic?
Well, I think three magic "find" oneliners could do the job. I will try
and see.
Wolfgang.
next prev parent reply other threads:[~2017-03-03 16:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 14:18 [Buildroot] [RFC PATCH 0/9] Make the buildroot toolchain relocatable Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 1/9] package/patchelf: use a recent version and add "--make-rpath-relative" patch Wolfgang Grandegger
2017-03-04 11:26 ` Arnout Vandecappelle
2017-03-04 15:16 ` Wolfgang Grandegger
2017-03-05 23:13 ` Arnout Vandecappelle
2017-03-06 8:42 ` Wolfgang Grandegger
2017-03-06 12:40 ` Arnout Vandecappelle
2017-03-06 13:57 ` Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 2/9] support/scripts: add fix-rpath script to sanitize the rpath Wolfgang Grandegger
2017-03-03 14:48 ` Thomas Petazzoni
2017-03-03 16:39 ` Wolfgang Grandegger [this message]
2017-03-06 9:07 ` Wolfgang Grandegger
[not found] ` <30db8390-0a94-5449-0c5e-90263576be98@mind.be>
2017-03-07 9:13 ` Wolfgang Grandegger
[not found] ` <7524a67f-d19d-1023-262c-c0b7793e6066@mind.be>
2017-03-08 9:25 ` Wolfgang Grandegger
2017-03-12 20:53 ` Arnout Vandecappelle
2017-03-12 21:10 ` Wolfgang Grandegger
2017-03-13 17:08 ` Arnout Vandecappelle
2017-03-14 7:36 ` Wolfgang Grandegger
2017-03-04 11:39 ` Arnout Vandecappelle
2017-03-04 15:29 ` Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 3/9] core: sanitize HOST_DIR at the very end of the build Wolfgang Grandegger
2017-03-04 11:50 ` Arnout Vandecappelle
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 4/9] core: add {TARGET, STAGING}_SANITIZE_RPATH_HOOK to TARGET_FINALIZE_HOOKS Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 5/9] support/scripts: add create-relocation-script for toolchain relocation Wolfgang Grandegger
2017-03-16 17:51 ` Arnout Vandecappelle
2017-03-17 7:10 ` Wolfgang Grandegger
2017-03-17 15:50 ` Arnout Vandecappelle
2017-03-17 17:15 ` Wolfgang Grandegger
2017-03-17 22:09 ` Arnout Vandecappelle
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 6/9] core: create relocate-toolchain.sh in HOST_DIR/usr at the end of the build Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 7/9] external-toolchain: check if a buildroot toolchain has already been relocated Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 8/9] support/scripts: check-host-rpath now handles $ORIGIN as well Wolfgang Grandegger
2017-03-03 14:46 ` Thomas Petazzoni
2017-03-03 14:56 ` Wolfgang Grandegger
2017-03-03 17:12 ` Wolfgang Grandegger
2017-03-03 14:18 ` [Buildroot] [RFC PATCH 9/9] support/scripts: check-host-rpath now uses patchelf to get the rpath Wolfgang Grandegger
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=c8a4d85e-ff1a-44ab-832b-bd4eff235a00@grandegger.com \
--to=wg@grandegger.com \
--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