From: Jan Rovins <janr@adax.com>
To: octane indice <octane@alinto.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Cross compiling MIPS kernel under x86
Date: Mon, 24 May 2010 10:32:12 -0400 [thread overview]
Message-ID: <4BFA8DEC.3070808@adax.com> (raw)
In-Reply-To: <1274711094.4bfa8c3675983@www.inmano.com>
octane indice wrote:
> Hello
>
> I have an octeon board. I'm trying to use a custom kernel from kernel.org
> instead of the Cavium one.
>
> Under x86, I installed the CrossTools from kegel:
> http://www.kegel.com/crosstool/
>
> I tried to cross compile:
> octane@darkstar:/opt/linux-2.6.34$ make ARCH=mips
> CROSS_COMPILE=/opt/crosstool/gcc-3.4.5-glibc-2.3.6/mips-unknown-linux-gnu/bin/mips-unknown-linux-gnu-
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> Checking missing-syscalls for N32
> CALL scripts/checksyscalls.sh
> Checking missing-syscalls for O32
> CALL scripts/checksyscalls.sh
> CALL scripts/checksyscalls.sh
> CC scripts/mod/empty.o
> Assembler messages:
> Error: Bad value (octeon) for -march
> make[2]: *** [scripts/mod/empty.o] Error 1
> make[1]: *** [scripts/mod] Error 2
> make: *** [scripts] Error 2
>
> So, I'm obviously missing a thing, but what?
>
> Here is other information:
> octane@darkstar:/opt$ cat world.c
> #include <stdio.h>
> int main()
> {
> printf("Hello world!\n");
> return 0;
> }
> octane@darkstar:/opt$
> /opt/crosstool/gcc-3.4.5-glibc-2.3.6/mips-unknown-linux-gnu/bin/mips-unknown-linux-gnu-gcc
> -march=octeon -o hello world.c
> world.c:1: error: bad value (octeon) for -march
> octane@darkstar:/opt$
>
> octane@darkstar:/opt$ ls
> /opt/crosstool/gcc-3.4.5-glibc-2.3.6/mips-unknown-linux-gnu/bin/
> fix-embedded-paths* mips-unknown-linux-gnu-gcov*
> mips-unknown-linux-gnu-addr2line* mips-unknown-linux-gnu-gprof*
> mips-unknown-linux-gnu-ar* mips-unknown-linux-gnu-ld*
> mips-unknown-linux-gnu-as* mips-unknown-linux-gnu-nm*
> mips-unknown-linux-gnu-c++* mips-unknown-linux-gnu-objcopy*
> mips-unknown-linux-gnu-c++filt* mips-unknown-linux-gnu-objdump*
> mips-unknown-linux-gnu-cpp* mips-unknown-linux-gnu-ranlib*
> mips-unknown-linux-gnu-g++* mips-unknown-linux-gnu-readelf*
> mips-unknown-linux-gnu-gcc* mips-unknown-linux-gnu-size*
> mips-unknown-linux-gnu-gcc-3.4.5* mips-unknown-linux-gnu-strings*
> mips-unknown-linux-gnu-gccbug* mips-unknown-linux-gnu-strip*
>
> So, is it a problem with octeon arch and gcc, or a mips problem?
>
> Thanks
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------------------
>
>
> Envoyé avec Inmano, ma messagerie renversante et gratuite : http://www.inmano.com
>
>
>
>
gcc-3.4.5-glibc-2.3.6
The recognition of "octeon" as an option does not show up in GCC until mainstream version 4.4.
looks like your gcc is too old
gcc-3.4.5-glibc-2.3.6
Jan
next prev parent reply other threads:[~2010-05-24 14:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 14:24 Cross compiling MIPS kernel under x86 octane indice
2010-05-24 14:32 ` Jan Rovins [this message]
2010-05-24 14:33 ` Dmitri Vorobiev
2010-05-25 13:13 ` Ralf Baechle
2010-05-25 13:48 ` Guenter Roeck
2010-05-25 13:58 ` octane indice
2010-05-25 14:44 ` Ralf Baechle
2010-05-26 13:11 ` octane indice
2010-05-26 14:26 ` Dmitri Vorobiev
2010-05-27 16:29 ` octane indice
2010-05-27 21:12 ` Dmitri Vorobiev
2010-05-27 21:34 ` David Daney
2010-05-27 22:17 ` Dmitri Vorobiev
2010-06-08 21:57 ` Phil Staub
2010-06-09 14:48 ` octane indice
2010-06-09 14:48 ` octane indice
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=4BFA8DEC.3070808@adax.com \
--to=janr@adax.com \
--cc=linux-mips@linux-mips.org \
--cc=octane@alinto.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 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.