| To: | vasanth <vasanth@aelixsystems.com> |
|---|---|
| Subject: | Re: unresolved symbol |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Thu, 8 Sep 2005 15:05:13 +0100 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <005201c5b47d$20a0d4d0$3c00a8c0@vasanth> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <005201c5b47d$20a0d4d0$3c00a8c0@vasanth> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.1i |
On Thu, Sep 08, 2005 at 07:26:17PM +0530, vasanth wrote: > I am getting the folowing error message when i do insmod . > insmod: unresolved symbol __udelay > insmod: unresolved symbol atomic_add > insmod: unresolved symbol atomic_sub > > I complied the driver code for mips processor using the folowing command > mips-linux-gcc -G O -mno-abicalls -fno-pic -pipe -mtune=4kc -mips32 -c > lcddriver.c -I/mykernel/include > It is compiling without any error . Use -O2. In fact use _exactly_ the same options as for the kernel build itself. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: MIPS SF toolchain, Dan Kegel |
|---|---|
| Next by Date: | Re: MIPS SF toolchain, David Daney |
| Previous by Thread: | unresolved symbol, vasanth |
| Next by Thread: | Re: unresolved symbol, Daniel Jacobowitz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |