From: Ralf Baechle <ralf@linux-mips.org>
To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Cc: octane indice <octane@alinto.com>, linux-mips@linux-mips.org
Subject: Re: Cross compiling MIPS kernel under x86
Date: Tue, 25 May 2010 14:13:41 +0100 [thread overview]
Message-ID: <20100525131341.GA26500@linux-mips.org> (raw)
In-Reply-To: <AANLkTinOaPkOXm128trTQ39jNGWMcvPhVUGWSQz6hLjR@mail.gmail.com>
On Mon, May 24, 2010 at 05:33:01PM +0300, Dmitri Vorobiev wrote:
> It looks like your toolchain is quite old. I just tried building a
> Cavium Octeon defconfig using my custom toolchain based on GCC 4.3.1
> and binutils 2.19.51.20090304, and the build was successfull. Before
> you ask: yes, GCC did receive `-march=octeon' :)
Tools requirements to build a kernel have become a little bit confusing.
I'm sure there are more restrictions that I've forgot.
* The Lemote 2F defconfig requires binutils 2.20 to build.
* GCC 3.2 is a lost cause for building 64-bit kernels
* GCC 3.3 is broken but can just about be kludged to build a 64-bit kernel.
* GCC 4.4 or a patched older version is required to build a kernel O2 or
Indigo² with R10000 processors.
* GCC 3.2 used to work for the rest but it's a very long time since I
tested this for a modern kernel.
* Linux 2.6.29 and older need a GCC older than 4.4.0 to compile.
Ralf
next prev parent reply other threads:[~2010-05-25 13:13 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
2010-05-24 14:33 ` Dmitri Vorobiev
2010-05-25 13:13 ` Ralf Baechle [this message]
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=20100525131341.GA26500@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dmitri.vorobiev@gmail.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.