From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] quick steps for buildroot?
Date: Mon, 19 Dec 2011 08:30:27 +0100 [thread overview]
Message-ID: <201112190830.27132.arnout@mind.be> (raw)
In-Reply-To: <1324175614.84733.YahooMailNeo@web161206.mail.bf1.yahoo.com>
On Sunday 18 December 2011 03:33:34 Tim Judd wrote:
> I've been using buildroot to generate a i486 toolchain because I don't know how to do it myself.
>
>
> Would anyone be gentle enough to paraphrase/quick steps (no details necessary) of what tools to use, in the right order? I'm savvy enough to understand how in a list of items how they're put together, but I don't know what I need.
Download crosstool-NG and use its configure mechanism to create a cross-toolchain.
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: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
prev parent reply other threads:[~2011-12-19 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 2:33 [Buildroot] quick steps for buildroot? Tim Judd
2011-12-19 7:30 ` Arnout Vandecappelle [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=201112190830.27132.arnout@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