Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Basic stupid questions regarding buildroot
@ 2010-05-20 10:23 David Wooff
  2010-05-20 10:34 ` Peter Korsgaard
  2010-05-20 10:44 ` Cyril HAENEL
  0 siblings, 2 replies; 3+ messages in thread
From: David Wooff @ 2010-05-20 10:23 UTC (permalink / raw)
  To: buildroot

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.
 


This electronic transmission is strictly confidential and intended solely for the addressee(s). If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this email.  If you have received this email in error please notify the sender as soon as possible. Any views expressed within this email may not necessarily be the views held by Calrec Audio Ltd.  Calrec Audio Ltd have taken measures to ensure this email is free from computer viruses, however it is recommended that you also employ anti-virus measures on your computer systems.
Calrec Audio Ltd. Registered in England. Registration number: 02392336. WEEE registration number: WEE/JE0051TQ/PRO. Registered address: Nutclough Mill, Hebden Bridge, West Yorks, HX7 8EZ.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100520/61738ce7/attachment.html>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Basic stupid questions regarding buildroot
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2010-05-20 10:34 UTC (permalink / raw)
  To: buildroot

>>>>> "David" == David Wooff <David.Wooff@calrec.com> writes:

 David> Hi,
 David> sorry for these rather basic questions:

 David> 1.  If I download the latest version of buildroot, am I tied to
 David> a particular version of the kernel?  I current have an old
 David> buildroot (from late last year and kernel 2.6.30, but I'm going
 David> to download the latest buildroot because I'm having compilation
 David> problems (since I did a "clean") and it has been suggested that
 David> I use the latest version.  I currently build the kernel
 David> separately.

There's a limited number of kernel versions supported for any buildroot
release, but as you are compiling your kernel seperately you are
completely free to choose your kernel version.

The kernel headers version doesn't have to be the same as the kernel
version (it only has to be new enough to provide headers for whatever
features you need).

 David> 2. Regarding pre-requisite "packages" or build tools, if I have
 David> to manually download a toolset of some description, where does
 David> it have to live?  Is this automatically "known" by any
 David> application which might want to use it?  Is there a list of
 David> anything I need to manually install before attempting to build
 David> buildroot?

You mean stuff on the build host? We do a dependency check when you run
make and error out if anything in missing.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] Basic stupid questions regarding buildroot
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Cyril HAENEL @ 2010-05-20 10:44 UTC (permalink / raw)
  To: buildroot



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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-05-20 10:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox