From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] rpath and runpath
Date: Sun, 21 May 2017 07:15:12 +0200 [thread overview]
Message-ID: <20170521071512.5474167b@free-electrons.com> (raw)
In-Reply-To: <a76b77be-c123-81ff-69f7-26508465e3c4@ou.edu>
Hello,
On Sat, 20 May 2017 14:54:19 -0600, Steve Kenton wrote:
> Thanks for the information. Is this a long term project or something
> likely to happen in the next few releases?
I'm hoping to get something like this merge in the next few releases.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-21 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 13:55 [Buildroot] rpath and runpath Steve Kenton
2017-05-19 19:27 ` Thomas Petazzoni
2017-05-20 20:54 ` Steve Kenton
2017-05-21 5:15 ` 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=20170521071512.5474167b@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