All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-mips@linux-mips.org
Subject: Re: native gcc for mipsel / uClibc (building or binaries)?
Date: Sun, 12 Feb 2006 13:31:49 -0800	[thread overview]
Message-ID: <43EFA945.1030906@avtrex.com> (raw)
In-Reply-To: <43EF7C06.3080006@wpkg.org>

Tomasz Chmielewski wrote:
> I'm trying to cross-compile gcc to work on mipsel / uClibc, to run there 
> natively (that is, I want to compile on this mipsel / uClibc machine).
> 
> So far I have a cross compiler that builds binaries for mipsel/uClibc on 
> a x86 machine.
> 
> 
> According to crosstool HOWTO, "to do a Canadian Cross build with 
> crosstool, you have to run it three times:
> 
>    1. once to build a toolchain that runs on the build system and 
> generates code for the host system
>    2. once to build a toolchain that runs on the build system and 
> generates code for the target system
>    3. once to build a toolchain that runs on the host system and 
> generates code for the target system".
> 
> So I guess the first step is behind me, but I'm not sure how to do steps 
> 2 and 3.
> 
> Anyone knows how to do it?
> Or perhaps, there are already gcc binaries available for mipsel / uClibc?
> 

I have done it for mipsel-linux-glibc, however until last week gcc had 
no support for uClibc, so it will probably not work with uClibc without 
some patching to gcc.

The basic idea is that once you have a working cross toolchain just 
configure gcc and binutils with: --build=i686-pc-linux-glibc 
--target=mipsel-linux --host=mipsel-linux.  This will produce a native 
toolchain.  You will have to copy the compile time portions of the C 
library (include files and link time libraries) to the target, then you 
should be all set.

David Daney.

  parent reply	other threads:[~2006-02-13  0:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 18:18 native gcc for mipsel / uClibc (building or binaries)? Tomasz Chmielewski
2006-02-12 19:27 ` Ilya A. Volynets-Evenbakh
2006-02-12 20:19   ` Tomasz Chmielewski
2006-02-12 20:32     ` Ilya A. Volynets-Evenbakh
2006-02-12 20:49       ` Tomasz Chmielewski
2006-02-12 21:31 ` David Daney [this message]
2006-02-12 21:48   ` Tomasz Chmielewski
2006-02-13 10:35     ` Richard Sandiford

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=43EFA945.1030906@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mangoo@wpkg.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.