Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Relocatable host tools
Date: Fri, 11 Dec 2015 16:57:33 +0100	[thread overview]
Message-ID: <20151211165733.158cd59b@free-electrons.com> (raw)
In-Reply-To: <CAAXf6LWo1kud7n4pxUcd+yuU7Pz-BpaDF+ipv3Mwh4dZmjgvEA@mail.gmail.com>

Thomas,

On Fri, 11 Dec 2015 16:55:09 +0100, Thomas De Schampheleire wrote:

> Ah, clearly not! Thanks for the reference.
> (I did search in my gmail, but had deleted old mails a while back)
> 
> Are there blocking issues with these patches? There are still some
> open comments on v5 but no objections in that iteration.
> (I haven't reviewed the code myself yet).
> 
> Samuel, could you also share your view on the status of these patches?
> Are you planning a new iteration with Baruch's comments fixed?

My objection is that the host rpath checks is done in shell scripts,
and the target rpath mungling in python scripts. I'd like to use either
one or the other language, but not both.

I believe Samuel said he wanted to respin his series, to use python
scripts to also do the host rpath checks that were added by Yann.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-11 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11 14:11 [Buildroot] [RFC] Relocatable host tools Thomas De Schampheleire
2015-12-11 15:28 ` Thomas Petazzoni
2015-12-11 15:55   ` Thomas De Schampheleire
2015-12-11 15:57     ` Thomas Petazzoni [this message]
2015-12-11 17:28       ` Yann E. MORIN
2015-12-11 20:25         ` Thomas De Schampheleire
2015-12-13 15:09           ` Samuel Martin

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=20151211165733.158cd59b@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