From: sswapnee@in.ibm.com
To: linux-kernel@vger.kernel.org
Subject: Unresolved symbol problem
Date: Fri, 8 Dec 2000 18:16:00 +0530 [thread overview]
Message-ID: <CA2569AF.00470FB0.00@d73mta05.au.ibm.com> (raw)
Hello,
I am new to linux world and currently learning to write device drivers and
modules. This question might have been
repeated many times on the list but I havent found any satisfactory answer
in the archives hence I am posting this question
again. While loading the module, the insmod complains about several
unresolved symbols namely securebits, printk, dput, d_alloc_root,
__generic_copy_to_user etc. I am not using any of these but still I am
getting the errors. Can someone please
tell me why am I getting this error? How to resolve this error?
I am using Linux 2.4.0-test10 on Intel Pentium box.
Thanking you in anticipation
Swapneel
-
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:[~2000-12-08 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 12:46 sswapnee [this message]
2001-11-05 14:51 unresolved symbol problem Jim Liu
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=CA2569AF.00470FB0.00@d73mta05.au.ibm.com \
--to=sswapnee@in.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).