From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add sam-ba to at91sam926*_defconfig
Date: Mon, 16 Apr 2012 14:34:29 +0200 [thread overview]
Message-ID: <20120416123429.GO16641@game.jcrosoft.org> (raw)
In-Reply-To: <87ty0l9b9l.fsf@macbook.be.48ers.dk>
On 19:04 Sun 15 Apr , Peter Korsgaard wrote:
> >>>>> "Jean-Christophe" == Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> writes:
>
> Hi,
>
> >> You build buildroot ON ARM/PPC? That's very uncommon (well, gcc110 is
> >> ppc64 - But still). Nevertheless, nothing breaks by including sam-ba in
> >> the build, your host dir just gets a little bit bigger. In this case I
> >> would say the advantage for the common case (build on x86 for at91
> >> development) outweighs the minor disadvantage for your use case.
>
> Jean-Christophe> I've a quad Arm and a quad G4
>
> Both of those are significantly slower than a recent x86, but all the
> power to you for using it.
>
> Jean-Christophe> except you expect a packet you install to work I
> Jean-Christophe> expect to detect the HOST type and propose it only if
> Jean-Christophe> it work
>
> We don't have any concept of host type in Kconfig, so I don't see how we
> could possibly do that.
I did it on dtc
HOSTOS := $(shell uname -s | tr '[:upper:]' '[:lower:]' | \
sed -e 's/\(cygwin\).*/cygwin/')
this work on unix
Best Regards,
J.
next prev parent reply other threads:[~2012-04-16 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 13:06 [Buildroot] [PATCH] Add sam-ba to at91sam926*_defconfig Alexandre Belloni
2012-04-11 13:35 ` Thomas Petazzoni
2012-04-11 13:50 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-11 19:24 ` Alexandre Belloni
2012-04-15 9:19 ` Peter Korsgaard
2012-04-15 13:56 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-15 17:04 ` Peter Korsgaard
2012-04-16 12:34 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-04-16 13:23 ` Thomas Petazzoni
2012-04-16 13:31 ` Jean-Christophe PLAGNIOL-VILLARD
2012-04-15 9:23 ` Peter Korsgaard
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=20120416123429.GO16641@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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