From: Gabor Kerenyi <wom@tateyama.hu>
To: linux-mips@linux-mips.org
Subject: crosscompile doesn't work :(
Date: Mon, 28 Apr 2003 18:25:09 +0200 [thread overview]
Message-ID: <200304281825.09697.wom@tateyama.hu> (raw)
hi!
I'm totally new to MIPS and the bigger trouble that I'm also
new to cross compiling.
I will get a little MIPS board with PCMCIA, USB, serial,
Ethernet, 4Mb flash memory. I have to build a linux for it
from scratch but I have never done cross compiling before.
I use debian (Woody) and I installed the toolchain package,
configured for mipsel-linux, I built the binutils and gcc,
(binutils 2.12, gcc 3.2.3)
I did:
tpkg-make mipsel-linux
cd binutils
debuild
debi
tpkg-install-libc mipsel-linux
cd ../gcc-3.2.3
debuild
debi
I can compile a simple c code, but I can't compile the kernel.
I tried to compile 2.4.19 and I ran into trouble at the beginning:
the 'as' said that -mcpu option is not recognized. OK, I removed
this option. Then everything seemed to be fine but when the
compilation arrived to the arch/mips directiory than I got the
following error messages:
make[1]: Leaving directory `/usr/src/linux/arch/mips/math-emu'
make CFLAGS="-D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -fomit-frame-pointer -I /usr/src/linux/include/asm/gcc -G
0 -mno-abicalls -fno-pic -pipe -mips2 -Wa,--trap " -C arch/mips/sni
make[1]: Entering directory `/usr/src/linux/arch/mips/sni'
mipsel-linux-gcc -D__KERNEL__ -I/usr/src/linux/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -fomit-frame-pointer -I /usr/src/linux/include/asm/gcc -G
0 -mno-abicalls -fno-pic -pipe -mips2 -Wa,--trap -c int-handler.S -o
int-handler.o
/usr/src/linux/include/asm/mipsregs.h: Assembler messages:
/usr/src/linux/include/asm/mipsregs.h:562: Error: unrecognized opcode
`static inline void tlb_probe(void)'
/usr/src/linux/include/asm/mipsregs.h:563: Warning: rest of line
ignored; first ignored character is `{'
/usr/src/linux/include/asm/mipsregs.h:564: Error: unrecognized opcode
`__asm__ __volatile__('
/usr/src/linux/include/asm/mipsregs.h:565: Warning: rest of line
ignored; first ignored character is `"'
/usr/src/linux/include/asm/mipsregs.h:566: Warning: rest of line
ignored; first ignored character is `"'
/usr/src/linux/include/asm/mipsregs.h:567: Warning: rest of line
ignored; first ignored character is `"'
/usr/src/linux/include/asm/mipsregs.h:568: Warning: rest of line
ignored; first ignored character is `"'
/usr/src/linux/include/asm/mipsregs.h:569: Warning: rest of line
ignored; first ignored character is `}'
The board chose was only a test bacause I don't know anything about
the board I'm going to use. There is a nice Japanese page about it,
but I can't read it.
http://www.tcs-8000.info/products/
Can anyone help? I have to bulid a complete little system in 4Mb
within a month.
I also tried to build the cross compile environment from the sources
directly not using toolchain but I got much less success. it didn't
compile at all (gcc).
Thanks a lot,
Gabor
next reply other threads:[~2003-04-28 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 16:25 Gabor Kerenyi [this message]
2003-04-28 17:16 ` wait on vr4181 part 2 Steven Seeger
2003-04-28 17:16 ` Steven Seeger
2003-04-28 17:24 ` Jun Sun
2003-04-28 19:47 ` crosscompile doesn't work :( Jeff Baitis
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=200304281825.09697.wom@tateyama.hu \
--to=wom@tateyama.hu \
--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.