Re: Undefined symbols in 2.6.11-rc5-mm1

[Christoph Hellwig]

On Sat, Mar 05, 2005 at 10:19:23AM -0500, Kai Germaschewski wrote:
> 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.

Or rather get rid of librarz objects completely.  We manage to have explicit
depencies for 99% of our needs, do we really need a special cases that breaks
for most of it's current users?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/