From: Mike Fedyk <mfedyk@matchmail.com>
To: Gordon Stanton <coder101@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: large built-in.o
Date: Sun, 22 Feb 2004 21:59:52 -0800 [thread overview]
Message-ID: <20040223055952.GJ18563@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <20040223055328.D70BB23947@ws5-3.us4.outblaze.com>
On Mon, Feb 23, 2004 at 01:53:28PM +0800, Gordon Stanton wrote:
> Hi,
> Just a quick question. I was building 2.6.3 with allyesconfig and I noticed it was making many built-in.o files around the place. These are quite large object files
> Eg. in fs is
> 74992735 Feb 23 15:35 built-in.o
> 74Meg for the filesystems code and thats with even the individual .o files compiled with -Os
>
> I haven't noticed this happening before. Is it new for 2.6.x?
Turn off CONFIG_DEBUG_INFO
prev parent reply other threads:[~2004-02-23 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 5:53 Gordon Stanton
2004-02-23 5:59 ` Mike Fedyk [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=20040223055952.GJ18563@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=coder101@linuxmail.org \
--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
all inboxes | Powered by JetHome®