From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 3/4] Makefile: add TARGET_CLEAR_RPATH_HOOK to TARGET_FINALIZE_HOOKS
Date: Mon, 13 Jul 2015 16:44:21 +0300 [thread overview]
Message-ID: <20150713134420.GT2451@tarshish> (raw)
In-Reply-To: <1436784870-17417-3-git-send-email-s.martin49@gmail.com>
Hi Samuel,
On Mon, Jul 13, 2015 at 12:54:29PM +0200, Samuel Martin wrote:
> This patch introduces the TARGET_CLEAR_RPATH_HOOK hook fixing the ELF
> files' RPATH of the host tree (excluding the sysroot).
>
> After running this hook, the RPATH from any target ELF files is empty.
There are legitimate uses for RPATH. The ebtable package sets the ebtables
executable RPATH to /lib/ebtables to load its libeb*.so extensions. The sudo
package add RPATH to /usr/libexec/sudo in visudo. There may be more. How
should we handle these cases? Maybe add a per-package, per-executable RPATH
setting?
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:[~2015-07-13 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 10:54 [Buildroot] [PATCH v4 1/4] support/scripts: add fix_rpaths Samuel Martin
2015-07-13 10:54 ` [Buildroot] [PATCH v4 2/4] Makefile: add HOST_FIX_RPATH_HOOK to TARGET_FINALIZE_HOOKS Samuel Martin
2015-07-13 10:54 ` [Buildroot] [PATCH v4 3/4] Makefile: add TARGET_CLEAR_RPATH_HOOK " Samuel Martin
2015-07-13 11:05 ` Baruch Siach
2015-07-13 13:44 ` Baruch Siach [this message]
2015-07-13 14:48 ` Samuel Martin
2015-07-13 10:54 ` [Buildroot] [PATCH v4 4/4] Makefile: staging symlink uses a relative path Samuel Martin
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=20150713134420.GT2451@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