public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Josef E. Galea" <josefeg@euroweb.net.mt>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXPORT_SYMBOL question
Date: Mon, 28 Mar 2005 13:46:42 +0200	[thread overview]
Message-ID: <4247EEA2.1040006@euroweb.net.mt> (raw)
In-Reply-To: <20050328111953.GA20502@mars.ravnborg.org>

Sam Ravnborg wrote:

>On Mon, Mar 28, 2005 at 01:10:35PM +0200, Josef E. Galea wrote:
>  
>
>>Hi,
>>
>>I have 2 modules. The first one uses EXPORT_SYMBOL to make some function 
>>available to other modules. These prototypes for these functions were 
>>also put in a header file. Now the second module uses the functions the 
>>functions defined in the first module by and includes the afore 
>>mentioned header file. However when i'm compiling the module, I get a 
>>symbol underfined warning. When I load the module it works as expected. 
>>Is there any way to get rid of these warnings.
>>
>>Another problem I'm having is that when I load the second module I get 
>>`no version for "rbnode_initialize" found: kernel tainted.' 
>>(rbnode_initialize is one of the functions exported by the first 
>>module). Both MODULE_LICENSE("GPL"); and MODULE_VERSION are declared in 
>>the two modules. Is there anything I'm missing?
>>    
>>
>
>You need to compile both modules at the same time.
>Do something like this for your two modules foo and bar:
>
>modules/Makefile
>obj-y := foo/ bar/
>modules/foo/	<= Your foo module
>modules/bar/	<= Your bar module
>
>Then when building the modules stay in modules/ and
>execute:
>make -C <path-to-kernel-src> M=`pwd`
>
>And to install modules:
>make -C <path-to-kernel-src> M=`pwd` modules_install
>
>	Sam
>
>  
>
Thanks for your help. That solved both the warnings and the kernel 
tainted message.

Josef

      reply	other threads:[~2005-03-28 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 11:10 EXPORT_SYMBOL question Josef E. Galea
2005-03-28 11:19 ` Sam Ravnborg
2005-03-28 11:46   ` Josef E. Galea [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=4247EEA2.1040006@euroweb.net.mt \
    --to=josefeg@euroweb.net.mt \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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