From: Chris Dearman <chris@mips.com>
To: Shantanu Gogate <sagogate@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: mips gcc compile error : unrecognized opcode errors
Date: Fri, 26 Mar 2004 10:59:42 +0000 [thread overview]
Message-ID: <40640D1E.6050403@mips.com> (raw)
In-Reply-To: <20040326102917.53609.qmail@web60703.mail.yahoo.com>
Shantanu Gogate wrote:
> Hi,
> I am trying to cross compile a user mode application for mips and I am getting these error
> messages when trying to do that:
>
> /tmp/ccgvdHuk.s: Assembler messages:
> /tmp/ccgvdHuk.s:1270: Error: unrecognized opcode `btl $4,0($2)'
> /tmp/ccgvdHuk.s:1270: Error: unrecognized opcode `setcb $25'
> /tmp/ccgvdHuk.s:3124: Error: unrecognized opcode `btl $4,0($2)'
> /tmp/ccgvdHuk.s:3124: Error: unrecognized opcode `setcb $25'
> /tmp/ccgvdHuk.s:3769: Error: unrecognized opcode `btl $4,0($2)'
> /tmp/ccgvdHuk.s:3769: Error: unrecognized opcode `setcb $25'
These aren't MIPS opcodes. If they've been generated by the compiler
then something is going badly wrong... Could you rebuild this file with
the extra flags "-v --save-temps" and send me the compiler output and
the .i file generated by the compiler.
> I was able to successfully cross compile the kernel and busybox using the same cross
> toolchain(although i needed to use 5.03 for busybox). I am running these on a redhat 7.3 box (alse
What problems did you have building busybox with 5.06? Please send
me details of this as well.
Chris
--
Chris Dearman The Fruit Farm, Ely Road voice +44 1223 706206
MIPS Technologies (UK) Chittering, Cambs, CB5 9PH fax +44 1223 706250
prev parent reply other threads:[~2004-03-26 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 10:29 mips gcc compile error : unrecognized opcode errors Shantanu Gogate
2004-03-26 10:36 ` Maciej W. Rozycki
2004-03-29 6:21 ` Shantanu Gogate
2004-03-29 12:05 ` Maciej W. Rozycki
2004-03-26 10:59 ` Chris Dearman [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=40640D1E.6050403@mips.com \
--to=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=sagogate@yahoo.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