From: Nicu Popovici <octavp@isratech.ro>
To: linux-mips@oss.sgi.com
Subject: Kernel compile error.
Date: Fri, 05 Jan 2001 17:18:37 -0500 [thread overview]
Message-ID: <3A56483D.17B57BD5@isratech.ro> (raw)
Hello to you all,
I have the folowing cross toolchain ( binutils-2.10.1, egcs-1.0.3a , and
glibc-2.0.6) and I can crosscompile some c c++ files on my intel machine
and run the executables on the mips. BUT I can not cross compile the
kernel for mips. I get the following error
=======================================================================
/crossdev/bin/mips-linux-gcc -D__KERNEL__
-I/home/nicu/JUNGO/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -mno-split-addresses -D__SMP__ -pipe -c -o
init/main.o init/main.c
/home/nicu/JUNGO/linux/include/asm/io.h: In function `copro_timeout':
/home/nicu/JUNGO/linux/include/asm/io.h:87: `asm' operand requires
impossible reload
/home/nicu/JUNGO/linux/include/asm/io.h:87: `asm' operand requires
impossible reload
/home/nicu/JUNGO/linux/include/asm/bugs.h: In function `check_fpu':
In file included from init/main.c:34:
/home/nicu/JUNGO/linux/include/asm/bugs.h:137: internal error--insn does
not satisfy its constraints:
(insn 244 241 250 (set (reg:SI 66 accum)
(reg:SI 6 a2)) 170 {movsi_internal2} (insn_list 241
(insn_list:REG_DEP_ANTI 98 (insn_list:REG_DEP_OUTPUT 138
(insn_list:REG_DEP_ANTI 247 (insn_list:REG_DEP_ANTI 150 (nil))))))
(nil))
mips-linux-gcc: Internal compiler error: program cc1 got
fatal signal 6
make: *** [init/main.o] Error 1
[nicu@ares linux]$ {standard input}: Assembler messages:
{standard input}:47: Error: unrecognized opcode `movl
%cr0,$2'
{standard input}:52: Error: unrecognized opcode `movl
$2,%cr0'
{standard input}:100: Error: unrecognized opcode `andl
%esp,$5'
{standard input}:108: Error: unrecognized opcode `outb
accum,$7'
{standard input}:109: Error: unrecognized opcode `outb
%al,$0x80'
{standard input}:114: Error: unrecognized opcode `outb
accum,$7'
=======================================================================
I have to mention that egcs and glibc are tested and I know for sure
that this one are good.
Does anyone know something related to this ?
Regards,
Octav
next reply other threads:[~2001-01-05 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 22:18 Nicu Popovici [this message]
2001-01-05 20:39 ` Kernel compile error Maciej W. Rozycki
2001-01-06 17:27 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2004-11-11 8:09 Ho Tan
2004-11-11 8:09 ` Ho Tan
2004-11-11 12:38 ` 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=3A56483D.17B57BD5@isratech.ro \
--to=octavp@isratech.ro \
--cc=linux-mips@oss.sgi.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