From: Keith M Wesolowski <wesolows@foobazco.org>
To: Shay Deloya <shay@miya.sgi.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Creating a mips tool chain for mips3
Date: Tue, 19 Jun 2001 09:24:01 -0700 [thread overview]
Message-ID: <20010619092400.B6828@foobazco.org> (raw)
In-Reply-To: <01061919142200.12304@miya>
On Tue, Jun 19, 2001 at 07:14:22PM +0300, Shay Deloya wrote:
> How can I configure the gcc and glibc to be compiled as mips3 and not mips1
> by default ?
Getting libgcc built as non-mips1 is something I haven't figured out
yet. At least, not without gross hacks. glibc is easy - put -mips2
in CFLAGS when you call configure.
In any case you must not use mips3 userland on 32-bit kernels, on
account of 64-bit istructions being used. You must use mips2.
--
Keith M Wesolowski <wesolows@foobazco.org> http://foobazco.org/~wesolows
------(( Project Foobazco Coordinator and Network Administrator ))------
"Nothing motivates a man more than to see his boss put
in an honest day's work." -- The fortune file
prev parent reply other threads:[~2001-06-19 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 16:14 Creating a mips tool chain for mips3 Shay Deloya
2001-06-19 16:24 ` Keith M Wesolowski [this message]
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=20010619092400.B6828@foobazco.org \
--to=wesolows@foobazco.org \
--cc=linux-mips@oss.sgi.com \
--cc=shay@miya.sgi.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