From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dependant modules question
Date: Fri, 2 Jul 2004 10:01:51 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0407020952270.3789@chaos> (raw)
In-Reply-To: <40E556E5.90708@vlnb.net>
On Fri, 2 Jul 2004, Vladislav Bolkhovitin wrote:
> Hello,
>
> I need some assistance with the kernel build system. It looks like this
> topic is not covered anywhere, at least I didn't find anything.
>
> I have two modules, A and B, where B is dependant from A, i.e. uses some
> exported from it symbols. Both modules are built outside of the kernel
> tree.
>
> With A everything is fine, it's compiled and installed with other kernel
> modules in /lib/modules/2.6.7/extra.
>
> Then module B is built. Here I have a problem. Module A is not listed as
> the module from which B depends in .mod.c file, therefore there are
> "Undefined symbols" warnings and it is impossible to load B, even though
> A is loaded.
>
> So, the question is: what should I do to make A be seen as exporting
> some symbols by the kernel and its build system?
>
> The kernel is 2.4.7, EXPORT_SYMBOL() used in A as required.
>
> Thanks,
> Vlad
Did you execute `depmod -a` after putting your modules into the
default directories and their information into /etc/modules.conf ?
Example:
/etc/modules.conf
alias char-major-177 module-a # First to load
alias char-major-177 module-b # Second to load
alias char-major-177 off # All done
# cp module-a.o /lib/modules/`uname -r`/kernel/drivers/char
# cp module-b.o /lib/modules/`uname -r`/kernel/drivers/char
# depmod -a
The first time anybody tries to access a device with the major
number of 177, its modules will be loaded in the correct order
by modprobe.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-07-02 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 12:36 Vladislav Bolkhovitin
2004-07-02 14:01 ` Richard B. Johnson [this message]
2004-07-02 14:17 ` Vladislav Bolkhovitin
2004-07-02 15:34 ` Randy.Dunlap
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.LNX.4.53.0407020952270.3789@chaos \
--to=root@chaos.analogic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vst@vlnb.net \
/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®