From: Daniel Kegel <dank@kegel.com>
To: gcc@gcc.gnu.org, Jonathan Day <imipak@yahoo.com>
Cc: linux-mips@linux-mips.org, crossgcc <crossgcc@sources.redhat.com>
Subject: Re: Question regarding compiling a toolchain for a Broadcom SB1
Date: Thu, 08 Sep 2005 10:33:53 -0700 [thread overview]
Message-ID: <43207601.7020000@kegel.com> (raw)
Jonathan Day <imipak at yahoo dot com> wrote:
> Crosstool, for example, only supports 32-bit MIPS -
> and even then the build matrix is a pretty shade of
> red for the most part.
[ The build matrix: http://kegel.com/crosstool/current/buildlogs/ ]
There are quite a few combinations that build for 32-bit mips with crosstool, e.g.
mips-gcc-3.2.3-glibc-2.2.5
mips-gcc-3.2.3-glibc-2.3.2
mips-gcc-3.3.6-glibc-2.2.5
mips-gcc-3.3.6-glibc-2.3.5
mips-gcc-3.4.4-glibc-2.3.2-hdrs-2.6.11.2
mips-gcc-3.4.4-glibc-2.3.5-hdrs-2.6.11.2
mips-gcc-4.1-20050702-glibc-2.3.2-hdrs-2.6.11.2
mips-gcc-4.1-20050709-glibc-2.3.2-hdrs-2.6.11.2
so the situation isn't that dire.
For the record, I would be more than happy to add mips64 support to crosstool.
http://www.linux-mips.org/archives/linux-mips/2005-07/msg00189.html
http://documents.jg555.com/cross-lfs/mips64-64/cross-tools/glibc.html
http://documents.jg555.com/cross-lfs/mips64-64/cross-tools/gcc-final.html
mentions some patches that might be needed.
I haven't had time to chase them down and add them to crosstool,
but if anybody else felt like it, I'd gladly accept the patches.
I'm sure a lot of mips64 users would be very happy.
- Dan
next reply other threads:[~2005-09-08 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 17:33 Daniel Kegel [this message]
2005-09-08 21:11 ` Question regarding compiling a toolchain for a Broadcom SB1 Jonathan Day
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=43207601.7020000@kegel.com \
--to=dank@kegel.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=imipak@yahoo.com \
--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