From: Jim Wilson <wilson@specifix.com>
To: David Lee <receive4me@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: HELP: opcode not supported on this processor
Date: Fri, 29 Sep 2006 12:17:24 -0700 [thread overview]
Message-ID: <1159557444.2897.3.camel@localhost.localdomain> (raw)
In-Reply-To: <5ee285ba0609290632m6c5e3f35nbae45307a3398b86@mail.gmail.com>
On Fri, 2006-09-29 at 21:32 +0800, David Lee wrote:
> I could not figure it out in more than 2 hours. I don't even know what
> compliantion options used for kernel. I need more instructions and
> help.
To elaborate on what Thiemo said, take a look at
http://www.linux-mips.org/wiki/Modules
In particular, see the fourth sentence of the first paragraph. I think
this solves your problem.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
prev parent reply other threads:[~2006-09-29 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 9:35 HELP: opcode not supported on this processor David Lee
2006-09-29 9:47 ` Freddy Spierenburg
2006-09-29 9:59 ` David Lee
2006-09-29 11:11 ` David Lee
2006-09-29 11:08 ` Thiemo Seufer
2006-09-29 13:32 ` David Lee
2006-09-29 19:17 ` Jim Wilson [this message]
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=1159557444.2897.3.camel@localhost.localdomain \
--to=wilson@specifix.com \
--cc=linux-mips@linux-mips.org \
--cc=receive4me@gmail.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