This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Thu, 2004-04-15 15:53:39 +0530, Seshaprasad V <seshaprasad@alumnux.com>
wrote in message <1082024619.3514.147.camel@piper>:
> I am facing an issue, which I feel has something to do with the dynamic
> linking runtime support in linux for loadable kernel modules. Following
> is a description of the issue:
>
> I have a module which has an extern variable. The variable is declared
> in a statically linked part of the kernel(linux). When i try to load the
> module(using insmod), i get an unresolved symbol error. However when the
> driver is statically linked, i don't get the error.
Any variable (inside the statically linked kernel image) which modules
may use need to be spacifically exported via the EXPORT_SYMBOL() or
EXPORT_SYMBOL_GPL() macro. This is most probably why your module doesn't
get access to the given variable... But you didn't include a pointer to
your kernel module's source code, so we can't say for sure. (And it's
offtopic, because kernel modules are linked with in-kernel linker code,
which is not the GNU ld code ...)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
Attachment:
signature.asc
Description: Digital signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |