From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v2] package/patchelf: new host package
Date: Thu, 31 Jul 2014 23:55:01 +0200 [thread overview]
Message-ID: <20140731235501.333bc892@free-electrons.com> (raw)
In-Reply-To: <fc8f5090621f94da255a6191eec78125047eb318.1406760999.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Thu, 31 Jul 2014 00:57:16 +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.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Mike Zick <minimod@morethan.org>
> ---
> package/Config.in.host | 1 +
> package/patchelf/Config.in.host | 7 +++++++
> package/patchelf/patchelf.mk | 12 ++++++++++++
> 3 files changed, 20 insertions(+)
> create mode 100644 package/patchelf/Config.in.host
> create mode 100644 package/patchelf/patchelf.mk
>
> diff --git a/package/Config.in.host b/package/Config.in.host
> index 062c6c9..e05bbfa 100644
> --- a/package/Config.in.host
> +++ b/package/Config.in.host
> @@ -13,6 +13,7 @@ menu "Host utilities"
> source "package/omap-u-boot-utils/Config.in.host"
> source "package/openocd/Config.in.host"
> source "package/parted/Config.in.host"
> + source "package/patchelf/Config.in.host"
> source "package/pwgen/Config.in.host"
> source "package/sam-ba/Config.in.host"
> source "package/squashfs/Config.in.host"
> diff --git a/package/patchelf/Config.in.host b/package/patchelf/Config.in.host
> new file mode 100644
> index 0000000..d1c8375
> --- /dev/null
> +++ b/package/patchelf/Config.in.host
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_HOST_PATCHELF
> + bool "host patchelf"
> + help
> + PatchELF is a small utility to modify the dynamic linker
> + and RPATH of ELF executables.
> +
> + http://nixos.org/patchelf.html
> diff --git a/package/patchelf/patchelf.mk b/package/patchelf/patchelf.mk
> new file mode 100644
> index 0000000..1a8e48d
> --- /dev/null
> +++ b/package/patchelf/patchelf.mk
> @@ -0,0 +1,12 @@
> +################################################################################
> +#
> +# patchelf
> +#
> +################################################################################
> +
> +PATCHELF_VERSION = 0.8
> +PATCHELF_SITE = http://releases.nixos.org/patchelf/patchelf-0.8/
> +PATCHELF_LICENSE = GPLv3
The license is actually GPLv3+, see the README file of the project.
> +PATCHELF_LICENSE_FILES = COPYING
> +
> +$(eval $(host-autotools-package))
Other than that, applied, thanks!
I think it would be good to use that to make the toolchain relocatable,
instead of something like http://patchwork.ozlabs.org/patch/359841/.
What do you think?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-31 21:55 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
2014-07-31 6:41 ` Thomas De Schampheleire
2014-07-31 21:55 ` Thomas Petazzoni [this message]
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=20140731235501.333bc892@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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