From: Rahul Jain <rbj2@oak.njit.edu>
To: Kernel Traffic Mailing List <linux-kernel@vger.kernel.org>
Subject: How to add source files in kernel
Date: Fri, 4 Feb 2005 14:17:10 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.58.0502041408540.12006@chrome.njit.edu> (raw)
Hi All,
I am trying to add 2 new files (a .h and a .c) in the kernel. I copied my
.h file in /include/linux and .c in /net/core. I then made the
following change to the Makefile in /net/core.
obj-y := sock.o skbuff.o iovec.o datagram.o scm.o split_helper.o
where split_helper.o is for the .c file that I am adding.
The kernel recompilation went without any problems. I wrote loadable
module programs that can access the functions defined in .c. When I try to
install these modules, they came back with the following error
/sbin/insmod x.o
x.o: unresolved symbol enqueue_sfi
x.o: unresolved symbol init_skbuff_list
x.o: unresolved symbol get_head_sfi
x.o: unresolved symbol search_sfi
x.o: unresolved symbol enqueue_skbuff_list
x.o: unresolved symbol init_head_sfi
x.o:
Hint: You are trying to load a module without a GPL compatible license
and it has unresolved symbols. Contact the module supplier for
assistance, only they can help you.
make: *** [install] Error 1
These functions are defined in the .c file and declared with the extern
keyword in the .h file. In my modules I am including the .h file.
Any suggestions on what I might be missing here ?
Thanks,
Rahul.
next reply other threads:[~2005-02-04 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 19:17 Rahul Jain [this message]
2005-02-04 20:22 ` linux-os
2005-02-04 20:26 ` Kronos
2005-02-07 17:53 ` Rahul Jain
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=Pine.GSO.4.58.0502041408540.12006@chrome.njit.edu \
--to=rbj2@oak.njit.edu \
--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
all inboxes | Powered by JetHome®