From: Alberto Mattea <alberto@mattea.info>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Size difference in Kernel Modules
Date: Fri, 14 Jan 2011 18:58:35 +0100 [thread overview]
Message-ID: <201101141858.36264@alby> (raw)
In-Reply-To: <AANLkTi=DU3MpNd4-7a3-n2E3voPk25AtwdL93SxGcvn8@mail.gmail.com>
In data venerdì 14 gennaio 2011 18:47:41, anil joshi ha scritto:
> I have compiled kernel 2.6.35 but there is huge difference in size
> between 2.6.35.6-45.fc14.i686 (fedora core 14 ) and compiled one
> I am using same configuration file as fc14 uses
>
> following details show difference in size
>
>
> [Anil@localhost linux-2.6.35]$ du -h
> /lib/modules/2.6.35.6-45.fc14.i686/kernel/drivers/video/backlight/lcd.ko
> 8.0K
> /lib/modules/2.6.35.6-45.fc14.i686/kernel/drivers/video/backlight/lcd.ko
> [Anil@localhost linux-2.6.35]$ du -h
> /lib/modules/2.6.35/kernel/drivers/video/backlight/lcd.ko
> 160K /lib/modules/2.6.35/kernel/drivers/video/backlight/lcd.ko
> [Anil@localhost linux-2.6.35]$
>
>
> 62M /lib/modules/2.6.35.6-45.fc14.i686/
>
> 587M /lib/modules/2.6.35/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Usually when this happens to me it is because debugging symbols are included
in the build. Are you sure the configuration file has them disabled? On Ubuntu,
for instance, the configuration file which is described as the same used by
kernel packagers actually has debugging enabled.
Alberto
prev parent reply other threads:[~2011-01-14 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 17:47 Size difference in Kernel Modules anil joshi
2011-01-14 17:58 ` Alberto Mattea [this message]
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=201101141858.36264@alby \
--to=alberto@mattea.info \
--cc=linux-kernel@vger.kernel.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