From: Gorka guardiola <paurea@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Not able to see the symbols
Date: Tue, 30 Aug 2005 10:55:53 -0500 [thread overview]
Message-ID: <599f06db0508300855653289f2@mail.gmail.com> (raw)
I am programming a service in the kernel and want a module to be able to
use it. This means the module (an external module) need to see the symbols of
the variables (more specifically a lock and a list and some integers).
The problem is the when I compile
the kernel the symbols are not exported. I run nm or look at the System.map and
they are not there, so the module doesnt see them and says "symbol undefined"
when trying to link. Suprisingly, for some reason, it doesnt complain
about the lock.
I tried including (in the kernel service, and even though it is not a
module) module.h and using the EXPORT_SYMBOL macro to no avail.
I have also tried compiling the module two different ways (in the hope
that it would see the symbols even if I dont)
make -C /lib/modules/_kernelname_/build module SUBDIRS=$(pwd)
and
make -C /lib/modules/_kernelname_/build M=$(pwd)
where _kernelname_ is the name of my kernel.
Please, CC me on any answers, as I am not on the list.
TIA,
G.-
reply other threads:[~2005-08-30 15:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=599f06db0508300855653289f2@mail.gmail.com \
--to=paurea@gmail.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