From: Mike Fedyk <mfedyk@matchmail.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 71MB compressed for COMPILED(!!!) 2.6.0-test6
Date: Mon, 6 Oct 2003 01:38:03 -0700 [thread overview]
Message-ID: <20031006083803.GB1135@matchmail.com> (raw)
In-Reply-To: <1065428996.5033.5.camel@laptop.fenrus.com>
On Mon, Oct 06, 2003 at 10:29:56AM +0200, Arjan van de Ven wrote:
> On Mon, 2003-10-06 at 10:23, Mike Fedyk wrote:
> > Hi LK,
> >
> > A while back (after 2.6.0-test2-mm1 which came to 6.4MB compressed, and
> > 2.6.0-test3-mm2 which came out to 34MB compressed), I noticed that the file
> > sizes for compiled object code got a lot bigger. I reported it at the time,
> > but nobody was interested.
> >
> > Today after using 2.6.0-test4-mm3 for a few weeks, I decided to upgrade to
> > test6 and it's up to 71MB compressed!
>
>
> CONFIG_DEBUG_INFO=y
>
> makes the kernel be compiled with -g which gives it debuginfo, which
> basically ends up being the entire sourcecode included in the
> modules/kernel
>
Thanks Arjan.
config DEBUG_INFO
bool "Compile the kernel with debug info"
depends on DEBUG_KERNEL
help
If you say Y here the resulting kernel image will include
debugging info resulting in a larger kernel image.
Say Y here only if you plan to use gdb to debug the kernel.
If you don't debug the kernel, you can say N.
"Larger kernel image" yeah, NO SHIT! ;)
Maybe something that says it may enlarge your kernel by 5-10 times would be
nice...
next prev parent reply other threads:[~2003-10-06 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 8:23 71MB compressed for COMPILED(!!!) 2.6.0-test6 Mike Fedyk
2003-10-06 8:29 ` Arjan van de Ven
2003-10-06 8:38 ` Mike Fedyk [this message]
2003-10-06 10:24 ` Matthias Andree
2003-10-06 15:24 ` Jesper Juhl
2003-10-06 17:40 ` Mike Fedyk
2003-10-07 2:25 ` Matt Mackall
2003-10-06 17:46 ` jdow
2003-10-06 23:37 ` jw schultz
2003-10-07 20:31 ` Jesper Juhl
2003-10-07 21:31 ` Arthur Othieno
2003-10-06 9:05 ` Solved! was: " Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 8:49 Boszormenyi Zoltan
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=20031006083803.GB1135@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=arjanv@redhat.com \
--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