Re: lib.a causing modules not to load

[James Bottomley <James.Bottomley@steeleye.com>]

On Sun, 2003-11-16 at 20:47, Rusty Russell wrote:
> I think lib.a should be linked as is if !CONFIG_MODULES, and done as a
> ..o if CONFIG_MODULES.  Other alternatives are possible, but make it
> tricky if someone adds a module later which wants something in lib.a.

I tried this and it is getting to be a whole nasty mess can of worms:

You can't link the lib objects all in, because they can be overridden by
the arch dependent lib.a (we rely on link order to permit this).  For
instance on x86, dump_stack and bust_spinlocks give duplicate symbols.

If we have to add processing logic to work out what symbols are in the
arch lib.a, we might as well go the whole hog and try to work out what
is missing from the kernel and compile that alone as a module.

James