From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wireshark: remove RPATH tag
Date: Sun, 5 Apr 2015 12:06:44 +0200 [thread overview]
Message-ID: <20150405100644.GD4134@free.fr> (raw)
In-Reply-To: <20150405112958.781b5523@free-electrons.com>
Thomas, All,
On 2015-04-05 11:29 +0200, Thomas Petazzoni spake thusly:
> On Sun, 5 Apr 2015 11:05:00 +0200, Yann E. MORIN wrote:
> > > 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 have a series doing exactly that; I'll be sending it shortly.
>
> There was some concern in this thread that the approach to remove the
> rpath at the end of the build was indeed making the built-in rpath
> ineffective, but still present if you did a "strings" on the binary. Is
> this something you have a solution for?
Hmm... What I do is use patch-e;f to remove it altogether, yes.
Now, if there is another reference to it in another section (e.g. .data
or .rodata) I don't know. I can do a biggish test-build with lotta
packages and do a string on there, but I'm afraid we will find it in
those data sections, if only because some tools store the build dir and
some other things in there.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-04-05 10:06 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
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 [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=20150405100644.GD4134@free.fr \
--to=yann.morin.1998@free.fr \
--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