From: arrao@cdac.in (Raghavendra)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Huge difference in build sizes
Date: Wed, 03 Dec 2014 11:35:58 +0530 [thread overview]
Message-ID: <547EA846.9050405@cdac.in> (raw)
In-Reply-To: <20141203041526.GA5583@kroah.com>
On Wednesday 03 December 2014 09:45 AM, Greg KH wrote:
> On Wed, Dec 03, 2014 at 09:26:34AM +0530, Raghavendra wrote:
>> Hello Greg,
>>
>> Thank you for the reply.
>>
>> On Tuesday 02 December 2014 11:46 PM, Greg KH wrote:
>>> 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.
>> If you are referring to the option "CONFIG_DEBUG_INFO", then it is said to
>> 'y' in both the kernel's configuration files.
>> Is there any other config. option or compiler flags that I need to look for?
> That's a good one to turn off, start with that and see what happens.
>
Yeah, I turned off the config option and compared the sizes. Now, both
result in the same build size. Thanks for the suggestion Greg. Still, my
concern is that the distro's build is generating a small build size in
spite of having the option 'CONFIG_DEBUG_INFO' set to 'y'. Any thoughts?
Thanks,
Raghavendra
-------------------------------------------------------------------------------------------------------------------------------
[ C-DAC is on Social-Media too. Kindly follow us at:
Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
This e-mail is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. If you are not the
intended recipient, please contact the sender by reply e-mail and destroy
all copies and the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
is strictly prohibited and appropriate legal action will be taken.
-------------------------------------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2014-12-03 6:05 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
2014-12-03 3:56 ` Raghavendra
2014-12-03 4:15 ` Greg KH
2014-12-03 6:05 ` Raghavendra [this message]
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=547EA846.9050405@cdac.in \
--to=arrao@cdac.in \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).