Re: compile warning with EXPORT_SYMBOL
- From: Steve Sivier <ssivier1@xxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 08:13:44 -0800
In article <xk6Cf.39783$Kp.31619@xxxxxxxxxxxxxxxx>,
Ian Kilgore <invalid@xxxxxxxxxxxxxxx> wrote:
> Steve Sivier wrote:
> > 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
> Declare it extern?
As I said:
> > and module_function() is declared extern in a header that moduleB
(which is a typo and should say "moduleA_function() is declared extern",
sorry about that).
Thanks,
Steve
.
- References:
- compile warning with EXPORT_SYMBOL
- From: Steve Sivier
- Re: compile warning with EXPORT_SYMBOL
- From: Ian Kilgore
- compile warning with EXPORT_SYMBOL
- Prev by Date: Re: compile warning with EXPORT_SYMBOL
- Next by Date: invalid lvalue in unary '&' ... why? LKM
- Previous by thread: Re: compile warning with EXPORT_SYMBOL
- Next by thread: Re: compile warning with EXPORT_SYMBOL
- Index(es):
Relevant Pages
|
