From: Patrick Mansfield <patmans@us.ibm.com>
To: Lee <weifeil@usc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Use too large hard disk space when compiling the 2.6.0-testx
Date: Mon, 8 Dec 2003 17:02:55 -0800 [thread overview]
Message-ID: <20031208170255.A6425@beaverton.ibm.com> (raw)
In-Reply-To: <00a501c3bcfb$200b71e0$0300a8c0@tiger>; from weifeil@usc.edu on Sun, Dec 07, 2003 at 11:48:44AM -0800
On Sun, Dec 07, 2003 at 11:48:44AM -0800, Lee wrote:
> 1. Under kernel 2.6.0-testx, the compiling process always uses huge disk
> space.
Do you have CONFIG_DEBUG_INFO enabled? Try turning it off.
I have not tried to compile with it on but there were other complaints
about larger *kernel* images, and the config help (arch/i386/Kconfig)
says:
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.
-- Patrick Mansfield
prev parent reply other threads:[~2003-12-09 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 19:48 PROBLEM: Use too large hard disk space when compiling the 2.6.0-testx Lee
2003-12-09 1:02 ` Patrick Mansfield [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=20031208170255.A6425@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=weifeil@usc.edu \
/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.