Messages in this thread |  | | From | Torrey Hoffman <> | Subject | Unresolved symbol compiling a standalone module? | Date | Fri, 18 May 2001 15:41:20 -0700 |
| |
I'm compiling a standalone kernel module outside the kernel tree. The compile completes fine, but when I try to insmod it, I get:
unresolved symbol printk_R1b7d4074 unresolved symbol __const_udelay_Reae3dfd6
This is very strange, because a quick grep of some of the regular, loaded modules, like /lib/modules/2.2.19/net/eepro100.o, shows that they contain those exact symbols! So why are they "unresolved" in mine?
CONFIG_MODVERSIONS = 1, kernel is 2.2.19 + reiserfs, and I have checked my standalone module's makefile to ensure that it uses _exactly_ the same gcc options as the normal kernel modules.
My /usr/include/linux directory is a symbolic link to /usr/src/linux/include, and /usr/src/linux is the kernel I'm running.
What am I doing wrong?
Torrey Hoffman torrey.hoffman@myrio.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |