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-next>] [day] [month] [year] [list]
Message-ID: <309a667c0610070512y47718898i4a664ef6cce7c312@mail.gmail.com>
Date:	Sat, 7 Oct 2006 17:42:47 +0530
From:	"Devesh Sharma" <devesh28@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Compiling dependent module

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?

The source and makefile of both parent and dependent module is
attached with this mail.

Thanks
Devesh.

View attachment "hello.c" of type "text/x-csrc" (346 bytes)

Download attachment "Makefile" of type "application/octet-stream" (486 bytes)

View attachment "hello1.c" of type "text/x-csrc" (382 bytes)

Download attachment "Makefile" of type "application/octet-stream" (487 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ