linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Song Sam <samlinuxppc@yahoo.com.cn>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Module Compiling Problem
Date: Sun, 23 May 2004 20:34:59 +0200	[thread overview]
Message-ID: <20040523183459.GA2335@mars.ravnborg.org> (raw)
In-Reply-To: <20040523020029.65329.qmail@web15212.mail.bjs.yahoo.com>


On Sun, May 23, 2004 at 10:00:29AM +0800, Song Sam wrote:
>
> Song Sam <samlinuxppc@yahoo.com.cn> wrote
>
> > A error happened when I compiled a module.Could any warmhearted person
> > figure it out for me?
>
> OK,I did it by myself.:-)
> It turned out to be the fact that I enabled
> CONFIG_MODVERSIONS=y in kernel configuration
> and MODVERSIONS option in my module like
> #if defined(CONFIG_MODVERSIONS)
> #define MODVERSIONS
> #include <linux/modversions.h>
> #endif
> at the same time.They conflicted against each other.Is
> that so?A newbie error on module...

Looks wrong.
When compiling an external module use:
for 2.4:
make -C $ERNELSRC SUBDIRS=$PWD modules

for 2.6: (2.6.6 onwards)
make -C $KERNELSRC M=$PWD

	Sam

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-05-23 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22  0:57 Framebuffer problems Christopher E Cordahi
2004-05-22  7:25 ` Module Compiling Problem Song Sam
2004-05-23  2:00   ` Song Sam
2004-05-23 18:34     ` Sam Ravnborg [this message]
2004-05-24  1:49       ` Song Sam
2004-05-24  5:06         ` Sam Ravnborg
2004-05-24  7:22           ` Query about KERNELLOAD Venkatesh Savithri Mahesh
2004-05-24 12:09             ` Mark Chambers
2004-05-24 15:17           ` Module Compiling Problem Song Sam

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=20040523183459.GA2335@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=samlinuxppc@yahoo.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).