From: SR (c) 2000 <admin@gamecoding.cjb.net>
To: linux-kernel@vger.kernel.org
Subject: problem exporting symbols from a lkm
Date: Sun, 28 Jan 2001 19:16:06 +0100 [thread overview]
Message-ID: <SAK.2001.01.28.calrnhkd@ahem> (raw)
Hello,
I'm kinda new to this kernel hacking thing. So excuse me for any stupid questions/remarks.
The problem I have occurs because I'm trying to install the rshaper software on my linux system.
I'm running:
Distribution: red hat 6.2
Kernel ver.: 2.2.14-5.0
System: i386
compiler: gcc
compiler ver.: gcc version egcs-2.91.66 19990314/linux (egcs-1.1.2 release)
The rshaper software requires you to modify the 8390 driver kernel module.
I had no problems modifying the 8390.c source to accomodate rshaper.
The problem is that the ne2k-pci.o uses symbols from the 8390.o driver.
these symbols are exported with the EXPORT_SYMBOL macro.
When I load the modified 8390.o (insmod 8390.o)
my /proc/ksyms shows that the exported symbols from 8390.o are different
from the other symbols because they have "_R__ver_" in front of them.
And when I load the ne2k-pci.o it complains that it can't find those symbols
that were supposed to be exported by 8390.o
I have looked around on the net and this problem seems related to the
CONFIG_MODVERSIONS bug. since I have no clue as to getting
these symbols to be exported correctly maybe someone can tell me
how to get around this problem.
the compile command I used to compile 8390.c was:
gcc -D__KERNEL__ -DEXPORT_SYMTAB -DMODULE -I/usr/src/linux/net/inet -Wall -Wstrict-prototypes -O6 -m486 -c 8390.c
greetings,
Willem van Doesburg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-28 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 18:16 SR 2000 [this message]
2001-01-29 0:12 ` problem exporting symbols from a lkm Keith Owens
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=SAK.2001.01.28.calrnhkd@ahem \
--to=admin@gamecoding.cjb.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.