Sam Ravnborg wrote:
> On Sat, Jan 21, 2006 at 06:27:36PM +0200, Jari Ruusu wrote:
> > 2) Try building external module A that exports some function, and then build
> > another external module B (separate package, only knows function
> > prototype) that uses said exported function. And I mean build it cleanly
> > without puking error messages on me. 2.4 and older kernel got that right,
> > but 2.6 is still FUBAR. Serious regression here.
>
> This was always possible using a kbuild file specifying all relevant
> modules. But accepting this is not always doable kbuild now add an
> additional method. build module a. copy Module.symvers from module a to
> module b. Voila, module b has full access to symbols from module a. This
> includes module versioning support. Both methods are documented in
> Documentation/kbuild/modules.txt now.
But that "copy Module.symvers from module A to module B" does not work in
these situations:
1) Module B does not know where module A source is.
2) Automatic package builder box may remove all traces of module A before
module B is built.
3) Automatic package builder box may build module B before module A.
How about this:
make M=/path/to/dir IGNORE_MISSING_SYMVER_ERRORS=1 modules
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Meaning: If symbol version is available, fine, use that. If some info is not
available, that is fine too. Just make it work without symbol versioning.
Killing those damn error messages should be enough.
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
