compile warning with EXPORT_SYMBOL

From: Steve Sivier <ssivier1@xxxxxxxxxxx>
Date: Thu, 26 Jan 2006 06:26:58 -0800

Hi,
I've written a couple modules for a 2.6 kernel, call them moduleA and
moduleB. moduleB requires the use of a function in moduleA, so in
moduleA I have a line like:
EXPORT_SYMBOL(moduleA_function);

and module_function() is declared extern in a header that moduleB
includes. During the compile of moduleB (actually the linking), I get a
warning that moduleA_function isn't defined, which is true. It won't be
defined until both modules are loaded. Everything works fine and
moduleB can use moduleA_function() just fine.

Is there any way to get rid of the warning?

Thanks,
Steve
.

Follow-Ups:
- Re: compile warning with EXPORT_SYMBOL
  - From: Ian Kilgore

Prev by Date: best way to determine disk connection type
Next by Date: Re: Serial communication, detecting parity bits
Previous by thread: best way to determine disk connection type
Next by thread: Re: compile warning with EXPORT_SYMBOL
Index(es):
- Date
- Thread

Relevant Pages

Re: compile warning with EXPORT_SYMBOL
... Or do you install them with two different make commands? ... The warning appears during the build process of moduleB. ...
(comp.os.linux.development.system)
Re: compile warning with EXPORT_SYMBOL
... The warning appears during the build process of moduleB. ... How do you install the modules? ...
(comp.os.linux.development.system)
Re: compile warning with EXPORT_SYMBOL
... > Steve Sivier wrote: ... >> moduleB. ... >> and module_functionis declared extern in a header that moduleB ... >> warning that moduleA_function isn't defined, ...
(comp.os.linux.development.system)
Re: compile warning with EXPORT_SYMBOL
... Steve Sivier wrote: ... I've written a couple modules for a 2.6 kernel, call them moduleA and moduleB. ... echo izn@xxxxxxxxxxxx|tr zwvq aeto ...
(comp.os.linux.development.system)