Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Gilad Rom <gilad@romat.com>
To: "Stephen P. Becker" <geoman@gentoo.org>
Cc: Scott Parker <whtghst1@direcway.com>,
	Mudeem Iqbal <mudeem@Quartics.com>,
	"'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: cross compiling gcc for mips
Date: Sun, 02 Jan 2005 19:46:30 +0200	[thread overview]
Message-ID: <41D83376.9040403@romat.com> (raw)
In-Reply-To: <41D828E9.2020109@gentoo.org>

Just incase you haven't tried it yet, I'd recommend
crosstool (http://kegel.com/crosstool/) a very nice
set of scripts to automate the toolchain building
process. Also, uClibc has a very nice toolchain
build script at http://www.uclibc.org/toolchains.html
(if you are aiming for an embedded target).

Gilad.

Stephen P. Becker wrote:
> Scott Parker wrote:
> 
>> How did you configure GCC?
>>
>> Mudeem Iqbal wrote:
>>
>>> Hi,
>>>
>>> I am building a toolchain for mips platform. I am using
>>>
>>> binutils-2.15
>>> gcc-3.4.3
>>> glibc-2.3.3
>>> linux-2.6.9    (from linux-mips.org)
>>>
> 
> Try using 2.4 headers instead.  I haven't had much success using 2.6 
> headers to build a mips (cross)toolchain.
> 
> Steve
> 
> 
> 

  reply	other threads:[~2005-01-02 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 11:32 cross compiling gcc for mips Mudeem Iqbal
2005-01-02 16:54 ` Scott Parker
2005-01-02 17:01   ` Stephen P. Becker
2005-01-02 17:46     ` Gilad Rom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-03  4:40 Mudeem Iqbal
2006-07-18  7:12 qi tao
2006-07-18 10:53 ` Maciej W. Rozycki
2006-07-18 12:47   ` Fuxin Zhang
2006-07-19 18:35 ` James E Wilson

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=41D83376.9040403@romat.com \
    --to=gilad@romat.com \
    --cc=geoman@gentoo.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mudeem@Quartics.com \
    --cc=whtghst1@direcway.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox