public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Li <jli@extremenetworks.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EXPORT_SYMBOL doesn't work
Date: Mon, 18 Mar 2002 11:11:46 -0800	[thread overview]
Message-ID: <3C963BF2.C9D78479@extremenetworks.com> (raw)
In-Reply-To: <2643.1016433275@kao2.melbourne.sgi.com>

Keith Owens wrote:
> 
> On Sun, 17 Mar 2002 22:25:16 -0800,
> Jason Li <jli@extremenetworks.com> wrote:
> >int (*fdbIoSwitchHook)(
> >                           unsigned long arg0,
> >                           unsigned long arg1,
> >                           unsigned long arg2)=NULL;
> >EXPORT_SYMBOL(fdbIoSwitchHook);
> >gcc -D__KERNEL__ -I/home/jli/cvs2/exos/linux/include -Wall
> >-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> >-fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> >-march=i686    -c -o br_ioctl.o br_ioctl.c
> >br_ioctl.c:26: warning: type defaults to `int' in declaration of
> >`EXPORT_SYMBOL'
> 
> #include <linux/module.h>
> 
> Also add br_ioctl.o to export-objs in Makefile.

Thanks alot. It works.

Now another problem with versioning. It seems even after I have the
following in my module c file the symbol generated is not versioned:

#define MODULE
#include <linux/modversions.h>
#include <linux/kernel.h>

When I do nm on the module, fdbIoSwitchHook is still a pure name without
the version info. Can you please tell me how to enable the versioning
for the symbol fdbIoSwitchHook?

Appreciate your help!

-Jason

  reply	other threads:[~2002-03-18 19:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18  6:25 EXPORT_SYMBOL doesn't work Jason Li
2002-03-18  6:34 ` Keith Owens
2002-03-18 19:11   ` Jason Li [this message]
2002-03-18 19:19     ` Tom Rini
2002-03-18 19:32       ` Jason Li
2002-03-18 19:43       ` Jason Li
2002-03-19  0:22         ` Tom Rini
2002-03-20  6:19           ` Jason Li
2002-03-18 19:45     ` Keith Owens

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=3C963BF2.C9D78479@extremenetworks.com \
    --to=jli@extremenetworks.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    /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