From: Maxim Osipov <maxim.osipov@gmail.com>
To: Bryan Althouse <bryan.althouse@3phoenix.com>
Cc: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: mips64 crosstool
Date: Wed, 13 Jul 2005 08:41:27 +0400 [thread overview]
Message-ID: <6097c4905071221414a929ed2@mail.gmail.com> (raw)
In-Reply-To: <20050712181447Z8226651-3678+2808@linux-mips.org>
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.
BR,
Maxim
On 7/12/05, Bryan Althouse <bryan.althouse@3phoenix.com> 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
>
>
>
>
>
next prev parent reply other threads:[~2005-07-13 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 18:15 mips64 crosstool Bryan Althouse
2005-07-13 4:41 ` Maxim Osipov [this message]
2005-07-18 18:53 ` Bryan Althouse
2005-07-18 18:53 ` Bryan Althouse
2005-07-18 19:00 ` Bryan Althouse
2005-07-18 19:00 ` Bryan Althouse
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=6097c4905071221414a929ed2@mail.gmail.com \
--to=maxim.osipov@gmail.com \
--cc=bryan.althouse@3phoenix.com \
--cc=linux-mips@linux-mips.org \
--cc=maxim@mox.ru \
/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