From: "Stephen P. Becker" <geoman@gentoo.org>
To: TheNop <TheNop@gmx.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Cross tool chain based on gcc-3.4.x
Date: Tue, 23 Nov 2004 20:29:11 -0500 [thread overview]
Message-ID: <41A3E3E7.7020701@gentoo.org> (raw)
In-Reply-To: <41A3CE25.7040406@gmx.net>
TheNop wrote:
> Hello,
>
> I try to get a cross compiler based on
> gcc-3.4.2
> glibc-2.3.2
> binutils-2.15
> working; without success.
>
> Is anyone using a cross compiler base on gcc-3.4.x for a mips big
> endian target?
>
> Best regarts
> TheNop
>
I've got a very recent i686->mips-unknown-linux-gnu cross-toolchain
available at:http://dev.gentoo.org/~geoman/mips-glibc-crosstools.tar.bz2
if you are too frustrated with building your own.
It includes gcc-3.4.3, glibc-2.3.4 (20041102), and binutils 2.15.91.0.2.
Steve
next prev parent reply other threads:[~2004-11-24 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 23:56 Cross tool chain based on gcc-3.4.x TheNop
2004-11-24 1:29 ` Stephen P. Becker [this message]
2004-11-24 22:53 ` TheNop
2004-11-24 23:05 ` TheNop
2004-11-25 1:34 ` Stephen P. Becker
2004-11-29 22:55 ` TheNop
2004-11-29 23:01 ` Stephen P. Becker
2004-11-29 23:17 ` TheNop
2004-11-24 11:13 ` Thomas Petazzoni
2004-11-24 23:00 ` TheNop
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=41A3E3E7.7020701@gentoo.org \
--to=geoman@gentoo.org \
--cc=TheNop@gmx.net \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox