From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Huge difference in build sizes
Date: Tue, 2 Dec 2014 10:16:04 -0800 [thread overview]
Message-ID: <20141202181604.GA15869@kroah.com> (raw)
In-Reply-To: <547D818B.7090307@cdac.in>
On Tue, Dec 02, 2014 at 02:38:27PM +0530, Raghavendra wrote:
> Hello all,
>
> I am using Ubuntu-12.04 which came with 3.2 kernel. Parallel to this,
> I've compiled and installed 3.12.1 kernel using the Ubuntu-3.2's
> configuration, and the compiler which came with the distro. I've noticed
> that there is a huge difference in the size of the .ko file between the
> Ubuntu's kernel and the kernel which I've compiled. Sample results are :
>
> $ du -sh usb-storage.ko
> It shows : 56K for the Ubuntu's 3.2 kernel
> 1.3M for the custom kernel that I've compiled
>
> I've tested the same thing for a simple hello world module :
> $ du -sh hello.ko
> It shows : 4.0k for the Ubuntu's 3.2 kernel
> 56k for the custom kernel that I've compiled
>
> What could be the reason for this huge amount of difference of storage
> space in spite of using the same config file and compiler?
You have not "stripped" the debug symbols from the kernel you built,
which is what Ubuntu does as part of their build process. I suggest
turning off that kernel configuration option, as it's probably not
needed for your development.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2014-12-02 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 9:08 Huge difference in build sizes Raghavendra
2014-12-02 11:51 ` Vinícius Tinti
2014-12-02 12:37 ` Raghavendra
2014-12-02 12:50 ` Vinícius Tinti
2014-12-02 12:51 ` Vinícius Tinti
2014-12-02 18:16 ` Greg KH [this message]
2014-12-03 3:56 ` Raghavendra
2014-12-03 4:15 ` Greg KH
2014-12-03 6:05 ` Raghavendra
2014-12-03 6:51 ` Anders Darander
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=20141202181604.GA15869@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.