[Top] [All Lists]

Re: mips64 crosstool

To: Bryan Althouse <>
Subject: Re: mips64 crosstool
From: Maxim Osipov <>
Date: Wed, 13 Jul 2005 08:41:27 +0400
Cc: Linux/MIPS Development <>
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta;; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=E4PgcbvG5rhW3jdczoklVsBS1BtLfGiPQEZ1xmLegJoHQ72NkW4DbYHMQD9IcfrHnGnOwYcpy3OBSOlRc2LJ5rBe2BM7L8ACPP15T2Hx//VJhNAd04eaYLaPqBgHqxvF5CfB94aA473bVTt98eiHQUdyzAtG/6wo6g3Ay03biNc=
In-reply-to: <>
Original-recipient: rfc822;
References: <>
When I was looking at crosstool, it had problems with miltiarch
support for mips. If you want to produce mips64 only tools, you'll
need patches from Maciej which are not there also. And take a look
into build matrix :)

Conclusion - mips is not very well supported in crosstool.


On 7/12/05, Bryan Althouse <> wrote:
> Is anyone using crosstool to produce a 64 bit mips compiler?
> I need to produce a gcc that will accept the -mabi=64 option. I have been
> able to generate a 32bit gcc with crosstool, using
> TARGET=mips-unknown-linux-gnu.  Must I change this to
> TARGET=mips64-unkown-linux-gnu to create a 64bit compiler?  I have tried
> this, but crosstool will fail.  It appears as if -mabi=n32 is passed to the
> native gcc during the build-glibc-headers step.  This of course causes the
> native gcc to give up.
> Are there any patches for mips64 tool chain build?
> Thanks to all.
> Bryan

<Prev in Thread] Current Thread [Next in Thread>