Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kuehn <Andreas.Kuehn@gin.de>
To: buildroot@busybox.net
Subject: [Buildroot] kernel image size depends on toolchain?
Date: Wed, 11 Jun 2008 09:40:07 +0200	[thread overview]
Message-ID: <484F8157.2050902@gin.de> (raw)

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

             reply	other threads:[~2008-06-11  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  7:40 Andreas Kuehn [this message]
2008-06-11  7:55 ` [Buildroot] kernel image size depends on toolchain? Peter Korsgaard
2008-06-11  8:38   ` Andreas Kuehn
2008-06-11  9:31     ` Peter Korsgaard
2008-06-11 10:20       ` Andreas Kuehn
2008-06-11 11:09         ` Peter Korsgaard
2008-06-11 13:00           ` Andreas Kuehn
2008-06-11 13:58             ` Peter Korsgaard
2008-06-11 15:08               ` [Buildroot] kernel image size depends on toolchain? -Solved- Andreas Kuehn
2008-06-11 19:24                 ` Peter Korsgaard
2008-06-11 21:30     ` [Buildroot] kernel image size depends on toolchain? Markus Heidelberg
2008-06-11  8:30 ` Matthew Dombroski
2008-06-11  8:49   ` Andreas Kuehn

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=484F8157.2050902@gin.de \
    --to=andreas.kuehn@gin.de \
    --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