From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sat, 4 Apr 2015 19:59:23 +0200 Subject: [Buildroot] [PATCH] wireshark: remove RPATH tag In-Reply-To: <0dae86e37516236d337e8433c63047504f1576f9.1415126141.git.baruch@tkos.co.il> References: <0dae86e37516236d337e8433c63047504f1576f9.1415126141.git.baruch@tkos.co.il> Message-ID: <20150404195923.154d3366@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Baruch Siach, On Tue, 4 Nov 2014 20:35:41 +0200, Baruch Siach wrote: > Edit libtool to remove RPATH from generated binaries. This is similar to > upstream commit making the same change when buiding RPMs. > https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commitdiff;h=a4a624e4c5 > > Signed-off-by: Baruch Siach > --- > package/wireshark/wireshark.mk | 6 ++++++ > 1 file changed, 6 insertions(+) I'm still not sure what to do with this. Yann, Gustavo, Samuel, some suggestions ? Should we introduce a final check in target-finalize to warn about binaries having invalid rpaths, and start fixing them one by one ? Or a more brutal approach where we remove all rpaths in target-finalize ? I'm a bit uncomfortable with having a fix for just one package without having a globally defined policy on how to handle this rpath mess. Opinions welcome. Thanks, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com