The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Scott Baker <smbaker@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: exported module symbols and warnings
Date: Mon, 16 Oct 2006 22:10:10 +0200	[thread overview]
Message-ID: <20061016201010.GC32232@uranus.ravnborg.org> (raw)
In-Reply-To: <35a82d00610161135t3d65bf2ei46631e69bf6f7f12@mail.gmail.com>

On Mon, Oct 16, 2006 at 11:35:13AM -0700, Scott Baker wrote:
> Hello,
> 
> I'm developing a pair of kernel modules. One module needs to export a
> symbol that will be used by the second module. I'm doing this by using
> EXPORT_SYMBOL(MySymbol) in the first module and declaring the symbol
> as extern in the second module. It works fine.
> 
> However, there are a couple of warnings that I'm trying to clean up.
> The first is when building the second module (the one that uses the
> symbol). It is: "*** Warning: "MySymbol" [filename] undefined!"
> 
> The second warning occurs when insmod'ing the second module. It is:
> "no version for "MySymbol" found: kernel tainted."
> 
> Can someone point me in the right direction? The modules are behaving
> fine, but the warning messages are a bit unsightly.
Try to read Documentation/kbuild/modules.txt - here you will read that
the trick is to use a common kbuild file for both modules.

And that should fix your "no version" error too since you will
then know the version info during build time.

	Sam

      reply	other threads:[~2006-10-16 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 18:35 exported module symbols and warnings Scott Baker
2006-10-16 20:10 ` Sam Ravnborg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061016201010.GC32232@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smbaker@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox