Date: Sat, 5 Mar 2005 10:19:23 -0500 (EST)
From: Kai Germaschewski <kai.germaschewski@unh.edu>
To: Adrian Bunk <bunk@stusta.de>
cc: Rusty Russell <rusty@rustcorp.com.au>, Andrew Morton <akpm@osdl.org>,
       Sam Ravnborg <sam@ravnborg.org>,
       Vincent Vanackere <vincent.vanackere@gmail.com>,
       <keenanpepper@gmail.com>,
       lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Undefined symbols in 2.6.11-rc5-mm1
In-Reply-To: <20050305130416.GA6373@stusta.de>
Message-ID: <Pine.LNX.4.44.0503051012530.20560-100000@chaos.sr.unh.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 812
Lines: 24

On Sat, 5 Mar 2005, Adrian Bunk wrote:

> And this can break as soon as the "unused" object files contains 
> EXPORT_SYMBOL's.
> 
> Is it really worth it doing it in this non-intuitive way?

I don't think it non-intuitive, it's how libraries work. However, as you 
say, it is broken for files containing EXPORT_SYMBOL.

The obvious fix for this case is the one that akpm mentioned way earlier 
in this thread, move parser.o into $(obj-y).

It should be rather easy to have the kernel build system warn you when you 
compile library objects exporting symbols.

--Kai


-
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/