From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] bctoolbox: disable rpath
Date: Wed, 15 Feb 2017 09:58:00 +0100 [thread overview]
Message-ID: <20170215095800.411ddf31@free-electrons.com> (raw)
In-Reply-To: <CAHXCMM+6jsq4k6p4Wcun5OhjUZVoL7nVjjEymHup4p5Kg1MkQw@mail.gmail.com>
Hello,
On Wed, 15 Feb 2017 07:12:28 +0100, Samuel Martin wrote:
> For target package, I think we should not set/force this option by the
> infra because some packages may install some kind-of private libraries
> elsewhere than in /usr/lib and set RPATH to in their binaries to find
> them (e.g.: sudo or iptables, though they are cmake-based packages.).
Hum, I didn't think about this, and you're probably right. If
CMAKE_SKIP_RPATH skips *all* rpath information, including some custom
one like pointing to /usr/lib/<foo>/, then we have to keep it indeed.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-15 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 22:43 [Buildroot] [PATCH 1/4] Revert "bctoolbox: fix typos and logic error" Jörg Krause
2017-02-14 22:44 ` [Buildroot] [PATCH 2/4] bctoolbox: add patch to fix static linking Jörg Krause
2017-02-14 22:44 ` [Buildroot] [PATCH 3/4] bctoolbox: fix mbedtls/polarssl dependency Jörg Krause
2017-02-14 22:44 ` [Buildroot] [PATCH 4/4] bctoolbox: disable rpath Jörg Krause
2017-02-15 5:28 ` Baruch Siach
2017-02-15 6:12 ` Samuel Martin
2017-02-15 8:58 ` Thomas Petazzoni [this message]
2017-02-15 8:56 ` Thomas Petazzoni
2017-02-19 15:07 ` Jörg Krause
2017-02-19 17:44 ` Thomas Petazzoni
2017-02-20 21:25 ` [Buildroot] [PATCH 1/4] Revert "bctoolbox: fix typos and logic error" Thomas Petazzoni
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=20170215095800.411ddf31@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