public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Anthony Chee" <anthony.chee@polyu.edu.hk>
To: "Bart Trojanowski" <bart@jukie.net>, <linux-kernel@vger.kernel.org>
Cc: <kbuild-devel@vger.kernel.org>, <kernelnewbies@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: undefined reference
Date: Tue, 26 Mar 2002 12:17:50 +0800	[thread overview]
Message-ID: <000701c1d47d$31daade0$ccd7fea9@winxp> (raw)
In-Reply-To: <004501c1d34f$32bda110$0100a8c0@winxp> <20020325164535.A5144@jukie.net>

Or let me say clearly.

The suitution is I want the kernel source use the symbol from module.

What I did in the module code are:
1. EXPORT_SYMBOL(func) in the source code of module
2. Set "extern int func()" in the module header

What I did in the kernel source code are:
1. Insert "func()" in the inode.c
2. Add the module header in the kernel source code

Then I use "make bzImage", I got no error message on compiling inode.c, but
I got

"fs/fs.o(.text+0x1377d): undefined reference to `func'"

in the linking stage.

I also set condition inode.c to check the existing of module before calling
func()

Thanks

Regards,
Anthony

----- Original Message -----
From: "Bart Trojanowski" <bart@jukie.net>
To: "Anthony Chee" <anthony.chee@polyu.edu.hk>;
<linux-kernel@vger.kernel.org>
Cc: <kbuild-devel@vger.kernel.org>; <kernelnewbies@vger.kernel.org>;
<linux-kernel@vger.kernel.org>
Sent: Tuesday, March 26, 2002 5:45 AM
Subject: Re: undefined reference




  reply	other threads:[~2002-03-26  4:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-24 16:16 undefined reference Anthony Chee
2002-03-25 21:45 ` Bart Trojanowski
2002-03-26  4:17   ` Anthony Chee [this message]
2002-03-26  5:49     ` Keith Owens
2002-03-30 14:19       ` Anthony Chee

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='000701c1d47d$31daade0$ccd7fea9@winxp' \
    --to=anthony.chee@polyu.edu.hk \
    --cc=bart@jukie.net \
    --cc=kbuild-devel@vger.kernel.org \
    --cc=kernelnewbies@vger.kernel.org \
    --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