[Buildroot] kernel image size depends on toolchain?

Andreas Kuehn Andreas.Kuehn at gin.de
Wed Jun 11 08:49:13 UTC 2008


Hey Matt!

In fact I was a little confused about your question but a found the flag 
  in the kernels .config file.

# CONFIG_BLK_DEV_INITRD is not set

And so, initrd is not active.



Matthew Dombroski wrote:
> Hi,
> Have you tried disabling the initrd stuff in the buildroot config?
> ~Matt
> 
> On Wed, Jun 11, 2008 at 7:40 PM, Andreas Kuehn <Andreas.Kuehn at gin.de> wrote:
>> Its probably one of these "again" questions but I couldn't get a
>> reasonable/sound answer.
>>
>> I'm building an arm rootfs and an 2.6.23.14 kernel with the actual svn
>> buildroot and uclibc. It works quite well but produces really large
>> kernel images.
>>
>> Created:      Tue Jun 10 11:45:43 2008
>> Image Type:   ARM Linux Kernel Image (uncompressed)
>> Data Size:    4528112 Bytes = 4421.98 kB = 4.32 MB
>>
>> With an old toolchain I can achive regular sizes:
>>
>> Created:      Tue Jun 10 13:44:26 2008
>> Image Type:   ARM Linux Kernel Image (uncompressed)
>> Data Size:    1412792 Bytes = 1379.68 kB = 1.35 MB
>>
>>
>> Unfortunately, the old toolchain has a buggy uclibc and I need a new
>> one. -- How can I fix that greedy kernel thing ? --
>>
>> Thanks in advance...
>> akuehn
>> _______________________________________________
>> buildroot mailing list
>> buildroot at uclibc.org
>> http://busybox.net/mailman/listinfo/buildroot
>>
> 



More information about the buildroot mailing list