From: "Tom Vrána" <tom@voda.cz>
To: linux-mips@ftp.linux-mips.org
Subject: crosscompiling and
Date: Sat, 15 Jan 2005 19:42:25 +0100 [thread overview]
Message-ID: <41E96411.90305@voda.cz> (raw)
Hi,
I'm just hopelesly stuck, trying to make a kernel 2.4.27 for mips SoC
ADM5120 (MIPS 4Kc). I have the code in a 2.4.18 kernel that I'm able to
compile. With the code merged in 2.4.27 most of the stuff works, but I
get the following assembler errors. Like if it doesn't recognize what's
C and what assembler code ? I am using gcc3.3 toolchain built with
uclibc with 2.4.27 kernel headers. and I do appreciate any help....
Tom
mipsel-linux-uclibc-gcc -D__KERNEL__
-I/store/devel/adm/linux-2.4.27-mipscvs-20050114/include -c -o
mipsIRQ.o mipsIRQ.S
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:
Assembler messages:
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:875:
Error: unrecognized opcode `static inline void tlb_probe(void)'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:876:
Warning: rest of line ignored; first ignored character is `{'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:877:
Error: unrecognized opcode `do {}while(0)'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:878:
Error: unrecognized opcode `__asm__ __volatile__('
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:879:
Warning: rest of line ignored; first ignored character is `"'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:880:
Warning: rest of line ignored; first ignored character is `"'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:881:
Warning: rest of line ignored; first ignored character is `"'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:882:
Error: unrecognized opcode `do {}while(0)'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:883:
Warning: rest of line ignored; first ignored character is `}'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:885:
Error: unrecognized opcode `static inline void tlb_read(void)'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:886:
Warning: rest of line ignored; first ignored character is `{'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:887:
Error: unrecognized opcode `do {}while(0)'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:888:
Error: unrecognized opcode `__asm__ __volatile__('
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:889:
Warning: rest of line ignored; first ignored character is `"'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:890:
Warning: rest of line ignored; first ignored character is `"'
/store/devel/adm/linux-2.4.27-mipscvs-20050114/include/asm/mipsregs.h:891:
Warning: rest of line ignored; first ignored character is `"'
---- SNIP ---- (few hundred more complaints from other included header
files)
--
Tomas Vrana <tom@voda.cz>
--------------------------
VODA IT consulting, Borkovany 48, 691 75
http://www.voda.cz/
phone: +420 519 419 416 mobile: +420 603 469 305 UIN: 105142752
next reply other threads:[~2005-01-15 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 18:42 Tom Vrána [this message]
2005-01-15 18:55 ` crosscompiling and Thiemo Seufer
2005-01-15 19:21 ` Tom Vrána
2005-01-15 19:47 ` Thiemo Seufer
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=41E96411.90305@voda.cz \
--to=tom@voda.cz \
--cc=linux-mips@ftp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox