[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706080838210.17480@localhost.localdomain>
Date: Fri, 8 Jun 2007 08:40:22 -0400 (EDT)
From: "Robert P. J. Day" <rpjday@...dspring.com>
To: Kyle McMartin <kyle@...onical.com>
cc: Christoph Pleger <Christoph.Pleger@...uni-dortmund.de>,
linux-kernel@...r.kernel.org
Subject: Re: Size of kernel modules
On Thu, 7 Jun 2007, Kyle McMartin wrote:
> On Wed, Jun 06, 2007 at 05:05:34PM +0200, Christoph Pleger wrote:
> > So, my question is the follwing: Is it an expected feature that the file
> > sizes of modules grow so much only because of a different cpu type and a
> > different localversion, or is there probably a bug in my build tools?
>
> The kernel is compiled with debug info so that we can strip it later to
> build two packages, one with debugging information intact, and one
> without it.
>
> If you disable CONFIG_DEBUG_KERNEL, things should go back to normal
> sizes for you.
grow so much compared to *which other modules*? the ones that came
with your distro? if that's the case, try installing your new modules
with
# make INSTALL_MOD_STRIP=1 modules_install
that makes a *huge* difference in the size of the installed modules,
as i learned when i first ran across this on my fedora core system.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists