From: Mike Fedyk <mfedyk@matchmail.com>
To: Jesper Juhl <jju@dif.dk>
Cc: Matthias Andree <matthias.andree@gmx.de>, linux-kernel@vger.kernel.org
Subject: Re: 71MB compressed for COMPILED(!!!) 2.6.0-test6
Date: Mon, 6 Oct 2003 10:40:52 -0700 [thread overview]
Message-ID: <20031006174052.GA2190@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0310061655070.26687@jju_lnx.backbone.dif.dk>
On Mon, Oct 06, 2003 at 05:24:48PM +0200, Jesper Juhl wrote:
>
> On Mon, 6 Oct 2003, Matthias Andree wrote:
>
> > On Mon, 06 Oct 2003, Mike Fedyk wrote:
> >
> > > 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...
> >
> > Send a patch...
> >
>
> How about this one? :
Looks good to me, but why is this config option arch specific? Are there
any archatectures that don't support DEBUG_INFO?
next prev parent reply other threads:[~2003-10-06 17:41 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
2003-10-06 10:24 ` Matthias Andree
2003-10-06 15:24 ` Jesper Juhl
2003-10-06 17:40 ` Mike Fedyk [this message]
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=20031006174052.GA2190@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=jju@dif.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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.