linux-kernel - Re: Compiling dependent module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 7 Oct 2006 20:19:36 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Devesh Sharma <devesh28@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Compiling dependent module

On Sat, Oct 07, 2006 at 05:42:47PM +0530, Devesh Sharma wrote:
> Hello all,
> 
> I have a situation where, I have one parent module in ../hello/
> directory which exports one symbol (g_my_export). I have a dependent
> module in ../hello1/ directory. Both have it's own makefiles.
> Compiling of parent module (hello.ko) is fine, but during compilation
> of dependent module (hello1.ko) I see a warning that g_my_export is
> undefined.
> 
> On the other hand when I do depmod -a and modprobe, dependent module
> inserts successfully in kernel.
> 
> I want to remove compile time warning. What should I do?

Compile both module in same go.
See Documentation/kbuild/modules.txt for a description.

In short create a kbuild file that points to both modules
so kbuild knows about both modules when it builds them.

	Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/