From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/python: Remove runtime library paths
Date: Tue, 1 Nov 2016 16:22:38 +0100 [thread overview]
Message-ID: <20161101162238.7fd4264b@free-electrons.com> (raw)
In-Reply-To: <20161030094226.32070-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 30 Oct 2016 10:42:26 +0100, Bernd Kuhls wrote:
> This patch re-adds the rebased version of python-2.7-011-no-rpath.patch
> which was removed with the 2.7.6 bump:
> https://git.busybox.net/buildroot/commit/package/python?id=7e960dc9da56d4a484b5480746aaf617ca491274
>
> Without this patch usr/lib/python2.7/lib-dynload/_bsddb.so contains
>
> $ output/host/usr/bin/i586-buildroot-linux-uclibc-readelf -a output/target/usr/lib/python2.7/lib-dynload/_bsddb.so | grep RPATH
> 0x0000000f (RPATH) Library rpath: [/home/buildroot/br2/output/host/usr/i586-buildroot-linux-uclibc/sysroot/usr/lib]
>
> With this patch:
>
> $ output/host/usr/bin/i586-buildroot-linux-uclibc-readelf -a output/target/usr/lib/python2.7/lib-dynload/_bsddb.so | grep RPATH
> $
I think the idea for rpath pollution is to have a global solution with
patchelf to remove bogus rpath from all target binaries. Samuel Martin
is working on this, maybe you can help?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-01 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 9:42 [Buildroot] [PATCH 1/1] package/python: Remove runtime library paths Bernd Kuhls
2016-11-01 15:22 ` Thomas Petazzoni [this message]
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=20161101162238.7fd4264b@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