From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: remove RPATH tag
Date: Mon, 17 Nov 2014 09:45:48 -0300 [thread overview]
Message-ID: <5469EDFC.3050208@zacarias.com.ar> (raw)
In-Reply-To: <20141117123315.GG2196@tarshish>
On 11/17/2014 09:33 AM, Baruch Siach wrote:
> It seems that libtool decides to set rpath based on .la files we have in
> staging. Some of them (e.g. glib provided libs, and libnl) set either
> 'dependency_libs' (glib) or 'libdir' (libnl) to paths under output/build or
> staging. wireshark also links its own libraries (e.g. wiretap, epan) using
> local source tree .la files. I'm not sure how to solve this in the general
> case. It probably requires fixing up all these .la files.
Hi.
There's a good briefing at https://wiki.debian.org/RpathIssue
Fixing up is nice, however doing it in a good manner will require many
autoreconfs and being proactive about it.
Stripping RPATHs is probably a faster way out (via chrpath).
In the end this could be considered as a build information leak, not
terribly useful but doesn't look good either.
Regards.
next prev parent reply other threads:[~2014-11-17 12:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 18:35 [Buildroot] [PATCH] wireshark: remove RPATH tag Baruch Siach
2014-11-05 7:15 ` Thomas Petazzoni
2014-11-05 7:22 ` Baruch Siach
2014-11-05 7:31 ` Thomas Petazzoni
2014-11-17 12:33 ` Baruch Siach
2014-11-17 12:45 ` Gustavo Zacarias [this message]
2014-11-17 13:32 ` Samuel Martin
2014-11-17 13:38 ` Baruch Siach
2015-04-04 17:59 ` Thomas Petazzoni
2015-04-05 9:05 ` Yann E. MORIN
2015-04-05 9:29 ` Thomas Petazzoni
2015-04-05 10:06 ` 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=5469EDFC.3050208@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.