From: Cyril HAENEL <chaenel@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Basic stupid questions regarding buildroot
Date: Thu, 20 May 2010 12:44:46 +0200 [thread overview]
Message-ID: <4BF5129E.7060607@free.fr> (raw)
In-Reply-To: <1A3C06457633904EAC567D23DA05171702AA8455@calrec-exch03.calrecaudio.com>
Le 20/05/2010 12:23, David Wooff a ?crit :
> Hi,
> sorry for these rather basic questions:
> 1. If I download the latest version of buildroot, am I tied to a
> particular version of the kernel? I current have an old buildroot
> (from late last year and kernel 2.6.30, but I'm going to download the
> latest buildroot because I'm having compilation problems (since I did
> a "clean") and it has been suggested that I use the latest version. I
> currently build the kernel separately.
> 2. Regarding pre-requisite "packages" or build tools, if I have to
> manually download a toolset of some description, where does it have to
> live? Is this automatically "known" by any application which might
> want to use it? Is there a list of anything I need to manually
> install before attempting to build buildroot?
> Many thanks,
> Dave W.
Hi, I can answer to the question 1 :
I use buildroot for an arm processoir based board, and I build the
kernel separately. I work with a 2.6.27 kernel, I use buildroot release
2010.02, and everything works well. Before I was using release 2009-02,
but I changed to 2010.02 for the same reason, compilation problems after
make clean ;)
So I alway use my 2.6.27 kernel, I just changed its configuration to use
EABI because buildroot release 2010.02 use EABI by default.
Regards,
Cyril HAENEL
--
Cyril Haenel
Registered Linux User #332632
prev parent reply other threads:[~2010-05-20 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 10:23 [Buildroot] Basic stupid questions regarding buildroot David Wooff
2010-05-20 10:34 ` Peter Korsgaard
2010-05-20 10:44 ` Cyril HAENEL [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=4BF5129E.7060607@free.fr \
--to=chaenel@free.fr \
--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.