From: Ralf Baechle <ralf@linux-mips.org>
To: Ho Tan <ho.tan@avantec.com.hk>
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel compile error
Date: Thu, 11 Nov 2004 13:38:15 +0100 [thread overview]
Message-ID: <20041111123815.GA23713@linux-mips.org> (raw)
In-Reply-To: <00df01c4c7c5$cffdad90$6e01a8c0@HughTan>
On Thu, Nov 11, 2004 at 04:09:48PM +0800, Ho Tan wrote:
> When compliation, everything go fine until the compiler compling entry.S which locate at arch/mips/kernel. and the Error message prompt.
>
> make[1]: Entering directory `/usr/eldk/usr/src/linux-mips/arch/mips/kernel'
> mips_4KC-gcc -D__ASSEMBLY__ -D__KERNEL__ -I/usr/eldk/usr/src/linux-mips/include -D_MIPS_SZLONG=32 -D_MIPS_SZPTR=32 -D_MIPS_SZINT=32 -g -G 0 -mno-abicalls -fno-pic -pipe -c -o entry.o entry.S
_MIPS_SZLONG etc. are defined by the compiler. If your tree has kludgery
such as defining _MIPS_SZLONG etc. you shouldn't be surprised to see
errors like this. It also seems to indicate that mips_4KC-gcc is not a
compiler for a mips*-linux* target.
> entry.S: Assembler messages:
> entry.S:225: Error: unrecognized opcode `reg_s $8,164($29)'
> entry.S:226: Error: unrecognized opcode `reg_s $8,164($29)'
And that's what you get from it. See include/asm-mips/asm.h for REG_S.
Ralf
next prev parent reply other threads:[~2004-11-11 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 8:09 Kernel compile error Ho Tan
2004-11-11 8:09 ` Ho Tan
2004-11-11 12:38 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-06 9:42 Kernel Compile error 鲁克文
2019-09-06 10:22 ` Jan Kiszka
2006-05-19 7:45 Kernel compile Error Penshoppe Estrada
2006-05-19 9:15 ` Adrian Bunk
2003-01-09 2:15 kernel compile error Rodrigo F. Baroni
2003-01-09 2:48 ` Joshua Kwan
2001-10-13 16:34 Kernel " Tobias Hahn
2001-01-05 22:18 Nicu Popovici
2001-01-05 20:39 ` Maciej W. Rozycki
2001-01-06 17:27 ` Ralf Baechle
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=20041111123815.GA23713@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ho.tan@avantec.com.hk \
--cc=linux-mips@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.