Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn At revision 20289 breakage
Date: Fri, 19 Oct 2007 10:20:36 +0200	[thread overview]
Message-ID: <00b101c81229$10e8caf0$01c4af0a@Glamdring> (raw)
In-Reply-To: 4718671F.3040005@asist.si

----- Original Message ----- 
From: "Babarovic Ivica" <ivica.babarovic@asist.si>
To: "Ulf Samuelsson" <ulf@atmel.com>
Cc: <buildroot@uclibc.org>
Sent: Friday, October 19, 2007 10:13 AM
Subject: Re: [Buildroot] svn At revision 20289 breakage


> Ulf Samuelsson wrote:
>>
>> It is always the case that you have to provide a ".config" file for 
>> linux.
>>
>> For some lucky souls Buildroot will do it for you.
>> This is when there is an appropriate definition somewhere in the target 
>> directory,
>> and if you have supplied the right kernel.
> Well, I guess I was lucky until now. I never provided any kernel or 
> .config files.
> I still fail to see why this is important for buildroot build. Kernel 
> headers?
>
> I have a .config file from a kernel I build. Should I put that into 
> buildroot process?
> What differences would it make?
>>


If you want buildroot to build the kernel for you,
you need to ensure that LINUX26_KCONFIG
is defined as a link to your ".config" file when
the linus kernel is built.

The difference is that it will be one less script to run
you will get the modules automatically inserted into the root file system,
and the result will be in the binaries directory.

With the Advanced Kernel Configuration, you should be able to build 
basically
any kernel version, and you are able to apply patches much more freely
than before.

If you use the same version as the kernel headers, then
your kernel version choice is rather limited, and
if you choose to go with the latest, then the kernel version
will be updated once or twice a month.

Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57 

  reply	other threads:[~2007-10-19  8:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 18:22 [Buildroot] svn At revision 20289 breakage Babarovic Ivica
2007-10-18 20:59 ` Ivan Kuten
2007-10-18 20:20   ` Ulf Samuelsson
2007-10-18 21:31     ` Ivan Kuten
2007-10-18 20:33       ` Ulf Samuelsson
2007-10-18 20:36       ` Ulf Samuelsson
2007-10-18 21:58         ` Ivan Kuten
2007-10-19  6:39         ` Babarovic Ivica
2007-10-19  7:32           ` Babarovic Ivica
2007-10-19  7:45           ` Ulf Samuelsson
2007-10-19  8:13             ` Babarovic Ivica
2007-10-19  8:20               ` Ulf Samuelsson [this message]
2007-10-19 10:21               ` Kuten Ivan
2007-10-19  8:35                 ` Ulf Samuelsson
2007-10-19 10:45                   ` Kuten Ivan

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='00b101c81229$10e8caf0$01c4af0a@Glamdring' \
    --to=ulf@atmel.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