Date: Mon, 24 Sep 2007 01:21:17 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Alexey Dobriyan <adobriyan@sw.ru>,
       linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Move kasprintf.o to obj-y
Message-Id: <20070924012117.7827f3c7.akpm@linux-foundation.org>
In-Reply-To: <20070924080948.GA8525@infradead.org>
References: <20070924071826.GA6757@localhost.sw.ru>
	<20070924074110.GA7721@infradead.org>
	<20070924075949.GA1742@uranus.ravnborg.org>
	<20070924080948.GA8525@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1738
Lines: 35

On Mon, 24 Sep 2007 09:09:48 +0100 Christoph Hellwig <hch@infradead.org> wrote:

> On Mon, Sep 24, 2007 at 09:59:49AM +0200, Sam Ravnborg wrote:
> > > Please kill lib-y while you're at it.  It's useless and a constant
> > > source of pain like this.
> > Kernel-bloat is another "constant source of pain".
> > But the troubles are that increased blot does not result in compiler erros.
> > 
> > And your proposal to kil lib-y is a counter-act here.
> 
> Killing lib-y doesn't create kernel bloat if done right.  Just introduce
> proper Kconfig dependencies for the truely optional parts.  But if you
> look at the list of objects in lib-y you'll see that they fall in basically
> three categories:
> 
>  (1) always used by core code - should be obj-y
>  (2) generic implementation for arch-specific functionality, should be
>      guarded by Kconfig for clarity reasons anyway
>  (3) library code often but not always used by code that's not always
>      built in.  Here we run into the move to obj-y to avoid compiler
>      warning when used as module issue all the time.  Adding a CONFIG
>      for the bigger onces actually avoids bloat over obj-y here, and
>      when it's small enough obj-y is a lot safer in the presence of
>      modular users
> 
> Really, trying to use the old static library use on demand concept simply
> doesn't fit the way the kernel is built with it's modules and dependencies.

yup, it duplicates what the config system does and is a common source of
problems.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/