From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Creating initrd
Date: Fri, 12 Oct 2012 16:12:51 +0200 [thread overview]
Message-ID: <20121012161251.3401e6c0@skate> (raw)
In-Reply-To: <1350049738.14474.52.camel@Homeserver>
Dear Chris Wilkinson,
Please don't reply to me directly: keep the Buildroot list Cc'ed.
On Fri, 12 Oct 2012 09:48:58 -0400, Chris Wilkinson wrote:
> I had been using crosstool to build the kernel but now I see that BR
> can do that and using crosstool is unnecessary. I cleaned the kernel
> tree and the tar.bz2 is now 89MB. It is here
>
> https://skydrive.live.com/redir?resid=834D8577B5544D4E!169&authkey=!
> AGZIOn-ye6O3anc
By crosstool, do you mean crosstool-ng? Or something else?
Both the old crosstool (that no-one should be using) and crosstool-ng
do *NOT* build the kernel, so what you're saying doesn't make sense
here. They use kernel /headers/ to build a toolchain, but that's all
they do with the kernel.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-10-12 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 14:05 [Buildroot] Creating initrd Chris Wilkinson
2012-10-11 14:48 ` Thomas Petazzoni
2012-10-11 15:16 ` Chris Wilkinson
2012-10-11 15:23 ` Thomas Petazzoni
2012-10-11 17:28 ` Chris Wilkinson
2012-10-11 18:53 ` Thomas Petazzoni
[not found] ` <1349988968.14474.34.camel@Homeserver>
[not found] ` <20121012091408.6184bb9f@skate>
[not found] ` <1350049738.14474.52.camel@Homeserver>
2012-10-12 14:12 ` Thomas Petazzoni [this message]
2012-10-12 15:19 ` Chris Wilkinson
2012-10-12 14:23 ` Thomas Petazzoni
2012-10-11 21:45 ` Chris Wilkinson
2012-10-12 7:10 ` Thomas Petazzoni
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=20121012161251.3401e6c0@skate \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.