From: Ralf Baechle <ralf@linux-mips.org>
To: Narendra Kulkarni <narendra@econtek.com>
Cc: "'Narendra Kulkarni'" <narendra@spacomp.com>, linux-mips@linux-mips.org
Subject: Re: errors while insmoding usb-skeleton.o (changed to suit our requirements)
Date: Tue, 26 Oct 2004 17:04:33 +0200 [thread overview]
Message-ID: <20041026150433.GA30620@linux-mips.org> (raw)
In-Reply-To: <000b01c4bb6a$f87b1580$0e00a8c0@narendra>
On Tue, Oct 26, 2004 at 08:19:14PM +0530, Narendra Kulkarni wrote:
> I am building a module usb-skeleton.o with following compiler options (The
> complier options are same as the options of used for building kernel)
>
> /opt/brcm/hndtools-mipsel-linux-3.2.3/bin/mipsel-linux-gcc -D__KERNEL__ -I/
> usr/src/mipslinux/src/linux/linux/include -Wall -Wstrict-prototypes -Wno-tri
> graphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I/usr/src/
> mipslinux/src/linux/linux/../../include -I/usr/src/mipslinux/src/linux/linux
> /include/asm/gcc -G
> -mno-abicalls -fno-pic -pipe -mips2 -mlong-calls -nostdinc -iwithprefix
> include -DKBUILD_BASENAME=usb-skeleton -c -o usb-skeleton.o usb-skeleton.c
>
> When insmoding the usb-skeleton.o, insmod usb-skeleton.o
> I am getting the following erros
> Using usb-skeleton.o
> insmod: Relocation overflow of type 4 for __copy_user
> insmod: Relocation overflow of type 4 for __copy_user
> insmod: Relocation overflow of type 4 for __copy_user
>
> Where am i going wrong. Help would be appreciated.
Seems your compiler command line is missing -DMODULE.
Ralf
next parent reply other threads:[~2004-10-26 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000b01c4bb6a$f87b1580$0e00a8c0@narendra>
2004-10-26 15:04 ` Ralf Baechle [this message]
2004-10-26 15:06 ` errors while insmoding usb-skeleton.o (changed to suit our requirements) Narendra Kulkarni
2004-10-26 15:06 ` Narendra Kulkarni
2004-10-26 15:22 ` Ralf Baechle
2004-10-27 6:30 ` Narendra Kulkarni
2004-10-27 6:30 ` Narendra Kulkarni
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=20041026150433.GA30620@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=narendra@econtek.com \
--cc=narendra@spacomp.com \
/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