From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] kernel size
Date: Mon, 03 Nov 2008 09:41:23 +0100 [thread overview]
Message-ID: <87ej1tp5fw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <000001c93d37$d5a696d0$80f3c470$@be> (steve caster's message of "Sun\, 2 Nov 2008 23\:10\:37 +0100")
>>>>> "steve" == steve caster <steve@c2root.be> writes:
steve> Hi all,
steve> I am trying to build a kernel with buildroot and are using a
steve> separate .config file which I made myself. The kernel is
steve> working, yet is about 90MB is size. This is unbelievable as I
steve> nearly don?t have any modules. What could make is so big?
Hard to know without any more details. How big is the kernel if you
compile it by hand with the buildroot cross compiler? What platform,
what is your buildroot and kernel .config's?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-11-03 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 22:10 [Buildroot] kernel size steve caster
2008-11-03 8:41 ` Peter Korsgaard [this message]
2008-11-03 15:05 ` steve at c2root.be
2008-11-03 10:15 ` Thomas Petazzoni
2008-11-03 10:26 ` Ivan Kuten
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=87ej1tp5fw.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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