From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v2] package/patchelf: new host package
Date: Thu, 31 Jul 2014 06:26:52 +0300 [thread overview]
Message-ID: <20140731032652.GF2480@tarshish> (raw)
In-Reply-To: <fc8f5090621f94da255a6191eec78125047eb318.1406760999.git.yann.morin.1998@free.fr>
Hi Yann,
On Thu, Jul 31, 2014 at 12:57:16AM +0200, Yann E. MORIN wrote:
> In some situations, users may want to tweak the dynamic section of the
> binaries (for example to add/set the RPATH to $ORIGIN/../lib).
>
> Because it is not trivial to do it properly from the Buildroot
> infrastructure, allow those users to use patchelf (e.g. from a
> post-build script) to tweak binaries.
>
> patchelf is able to:
> - modify an existing DT_RUNPATH tags
> - add a DT_RUNPATH tag if not already present
> - do the above to the DT_RPATH tag, too
> - set the path to the interpreter
> - remove DT_NEEDED tags
> - query a binary for the DT_RUNPATH/DT_RPATH tag, or for the
> interpreter path
>
> Does not really fix #7172, but this is an appropriate workaround.
Maybe this is worth a mention as a workaround to the known issue of #7172 in
the manual?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-07-31 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 22:57 [Buildroot] [PATCH 0/2 v2] Workaround for bug #7172: patchelf (branch yem/patchelf) Yann E. MORIN
2014-07-30 22:57 ` [Buildroot] [PATCH 1/2 v2] toolchain: linker options with a $ sign are not supported Yann E. MORIN
2014-07-31 6:38 ` Thomas De Schampheleire
2014-07-31 21:54 ` Thomas Petazzoni
2014-07-30 22:57 ` [Buildroot] [PATCH 2/2 v2] package/patchelf: new host package Yann E. MORIN
2014-07-31 3:26 ` Baruch Siach [this message]
2014-07-31 6:41 ` Thomas De Schampheleire
2014-07-31 21:55 ` Thomas Petazzoni
2014-07-31 22:05 ` Yann E. MORIN
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=20140731032652.GF2480@tarshish \
--to=baruch@tkos.co.il \
--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