From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] sam-ba: only propose it if the host is x86 or x86_64
Date: Mon, 07 May 2012 16:34:33 +0200 [thread overview]
Message-ID: <87d36gcb5y.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20120507134551.GB10138@game.jcrosoft.org> (Jean-Christophe PLAGNIOL-VILLARD's message of "Mon, 7 May 2012 15:45:51 +0200")
>>>>> "Jean-Christophe" == Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> writes:
Jean-Christophe> it's the for ping
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.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-05-07 14:34 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 [this message]
2012-05-07 15:57 ` Jean-Christophe PLAGNIOL-VILLARD
2012-05-11 19:42 ` Arnout Vandecappelle
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=87d36gcb5y.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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