lkml.org 
[lkml]   [2003]   [Nov]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: lib.a causing modules not to load
From
Date
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




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

\
 
 \ /
  Last update: 2005-03-22 13:58    [W:0.047 / U:0.148 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site