Re: Symbol Versioning [Was Re: Unresolved Symbol in Module]

[Peter Jay Salzman <p@dirac.org>]

hate to prolong this thread (i've been pretty silent until now, taking all
the info in).

i've added a bit more about modversions.h in mpg, but was getting the same
unresolved printk message.  however, mark hit the nail on the head.  assuming
we don't want to recompile a module every time we move on to a new
kernel version,

On Fri 09 Mar 01, 11:32 AM, Mark McLoughlin said: 
> 
> The simple answer to the question is that you need to include modversions.h
> before the header file for printk if you want the module to load into a kernel
> with CONFIG_MODVERSIONS turned on.
> 
> You could do this in two ways
> 
>    o in each of your c files, at the top (before you include linux/kernel.h)
> 
> #idef CONFIG_MODVERSIONS
> #include <linux/modversions.h>
> #endif

this seems to be the answer for now.  the good explanantion will be going
into mpg tonight.

john points out that modversions will be rewritten in linux 2.5.  this is
perfect evidence of why mpg should be a living document.   :-)

thanks for good dialog on the subject!

pete

ps- quite a few people asked to see the new version of the document.  it
would be really helpful to give me feedback on the new document.  it's
pretty different from the original, and i'm still trying to find my way.
i'm trying to strike a balance between not falling into rubini's trap of
giving too much info too quickly versus the not enough detail, which i felt
the original document might have done.   comments are encouraged.

pps- about formatting.  linuxdoc.sty is nothing short of bizarre.  non
standard page size(!) along with funky margins which are more appropriate for
a published book than a document.  i'm trying to iron out a new page format.
-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/
IRC Channel:   irc.openprojects.net / #kernelnewbies
Web Page:      http://www.surriel.com/kernelnewbies.shtml