Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] sam-ba: only propose it if the host is x86 or x86_64
Date: Fri, 11 May 2012 21:42:21 +0200	[thread overview]
Message-ID: <4FAD6B9D.9080604@mind.be> (raw)
In-Reply-To: <20120507155726.GC10138@game.jcrosoft.org>

On 05/07/12 17:57, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> >    Jean-Christophe>  did I need to understand that noe one care of non x86 host?
>> >
>> >  To me it is more of a question of tradeoffs. Either we do it really
>> >  right and use this kind of infrastructure for the external toolchains as
>> >  well (where it really matters), or we decide the extra complexity isn't
>> >  worth it for the few non-x86 users.
>> >
>> >  I haven't made up my mind about this yet, but am leaning towards the
>> >  2nd.
> as a non x86 user I really care
>
> and as the ARM A15 will come soon on the market for serer as example it will
> be more and more problematic for binary package

  ... except that it's not really problematic.  The only problem is that you can
configure buildroot to download something that won't actually run on your
system.  This problem is a lot worse for external toolchains than for sam-ba.

  That said, the patch is really simple and doesn't create a maintenance burden.
Having it in paves the way for disallowing other downloaded host binaries, and
for downloading host binaries for the correct platform.  Therefore:

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

  Jean-Christophe, maybe it's worthwhile to resend and perhaps add
a patch for external toolchains as well?

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-05-11 19:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 15:05 [Buildroot] [PATCH 1/2] add host arch detection and Kconfig (BR2_HOSTARCH) Jean-Christophe PLAGNIOL-VILLARD
2012-04-17 15:05 ` [Buildroot] [PATCH 2/2] sam-ba: only propose it if the host is x86 or x86_64 Jean-Christophe PLAGNIOL-VILLARD
2012-04-23  6:50   ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-27 10:19     ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-04  5:01       ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-07 13:45         ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-07 14:34           ` Peter Korsgaard
2012-05-07 15:57             ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-11 19:42               ` Arnout Vandecappelle [this message]
2012-04-28 15:38 ` [Buildroot] [PATCH 1/2] add host arch detection and Kconfig (BR2_HOSTARCH) Arnout Vandecappelle
2012-04-30 10:29   ` Jean-Christophe PLAGNIOL-VILLARD

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=4FAD6B9D.9080604@mind.be \
    --to=arnout@mind.be \
    --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