All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: octane indice <octane@alinto.com>
Cc: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Cross compiling MIPS kernel under x86
Date: Tue, 25 May 2010 15:44:00 +0100	[thread overview]
Message-ID: <20100525144400.GA30900@linux-mips.org> (raw)
In-Reply-To: <1274795905.4bfbd781a17fa@www.inmano.com>

On Tue, May 25, 2010 at 03:58:25PM +0200, octane indice wrote:

> Ok. I'm following the info there:
> http://www.linux-mips.org/wiki/Toolchains
> but infos seems a bit old, so I followed the main idea
> with newer binutils and gcc-4.4.4

That page just documents available toolchains and is suffering from too
many details.  Somebody should do a bit weed killing on that page.

The build dependencies for the kernel are documented on

  http://www.linux-mips.org/wiki/Kernel_Build

which I've updated just before my previous posting.

> It is still compiling gcc. When it will finish, I will ping back
> and say if it compiles an octeon kernel 2.6.34

It will :-)

  Ralf

  reply	other threads:[~2010-05-25 14:44 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
2010-05-25 13:48     ` Guenter Roeck
2010-05-25 13:58     ` octane indice
2010-05-25 14:44       ` Ralf Baechle [this message]
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=20100525144400.GA30900@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.