lib-y vs EXPORT_SYMBOL: who wins?

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: lkml - Kernel Mailing List <linux-kernel@...>
Cc: Sam Ravnborg <sam@...>, Andrew Morton <akpm@...>
Date: Tuesday, September 25, 2007 - 1:07 am

Various files under lib/ are linked into a .a so they only get linked if
needed.  But many of these functions are also EXPORT_SYMBOL()ed.

This doesn't really make sense: if it's exported it really needs to be
present.  Certain configurations can hit this (lguest uses kasprintf,
and can be a module).

We could do something hacky and try to figure out if any modules need
the symbols, which screws modules built later, but is no worse than a
CONFIG_-based solution.

Or to we just move all the exported functions out of the .a?

Cheers,
Rusty.

-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
lib-y vs EXPORT_SYMBOL: who wins?, Rusty Russell, (Tue Sep 25, 1:07 am)
Re: lib-y vs EXPORT_SYMBOL: who wins?, Sam Ravnborg, (Tue Sep 25, 2:13 am)