public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Shane Nay <shane@minirl.com>, Pavel Machek <pavel@suse.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mips@oss.sgi.com, linux-mips-kernel@lists.sourceforge.net
Subject: Re: Toolchains
Date: Tue, 17 Jul 2001 10:20:50 -0700	[thread overview]
Message-ID: <20010717102050.A21784@lucon.org> (raw)
In-Reply-To: <20010717083514.A19836@lucon.org> <Pine.LNX.4.10.10107170940420.16793-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10107170940420.16793-100000@transvirtual.com>; from jsimmons@transvirtual.com on Tue, Jul 17, 2001 at 09:41:14AM -0700

On Tue, Jul 17, 2001 at 09:41:14AM -0700, James Simmons wrote:
> 
> > The toolchain in my RedHat 7.1 mips port is as good as the x86 version
> > for RedHat 7.1. Since there is no mips maintainer for gcc, many
> > mips patches aren't reviewed. But they are in my mips toolchain.
> 
> Where are they? On the oss.sgi.com site.

My mini-port of RedHat 7.1 is at

ftp://oss.sgi.com/pub/linux/mips/redhat/7.1/

you should be able to put a small RedHat 7.1 on the mips/mipsel box and
compile the rest of RedHat 7.1 yourselves.

Here are something you should know:

1. The cross compiler hosted on RedHat 7.1/ia32 is provided as a
toolchain rpm. The binary rpms for the mips and mipsel cross compilers
are included. You will need glibc 2.2.3-11 or above to use those
rpms. The glibc x86 binary rpms under RPMS/i386 should be ok.
2. You have to find a way to put those rpms on your machine. I use
network boot and NFS root to do it.
3. install.tar.bz2 has some scripts to prepare NFS root and install
RedHat 7.1 on a hard drive.

Thanks.


H.J.

      reply	other threads:[~2001-07-17 17:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22 20:57 [ANNOUNCE] Secondary mips tree James Simmons
2001-06-30 14:57 ` Pavel Machek
2001-07-08 18:32   ` James Simmons
2001-07-09 12:02     ` Pavel Machek
2001-07-12 21:47       ` strange 2.4.x problems with dual machine ognen
2001-07-13 15:01       ` [ANNOUNCE] Secondary mips tree James Simmons
2001-07-16 10:22         ` Shane Nay
2001-07-16 19:27           ` [Linux-mips-kernel] " James Simmons
2001-07-17  7:16             ` Shane Nay
2001-07-17 15:35               ` H . J . Lu
2001-07-17 16:41                 ` Toolchains James Simmons
2001-07-17 17:20                   ` H . J . Lu [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=20010717102050.A21784@lucon.org \
    --to=hjl@lucon.org \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips-kernel@lists.sourceforge.net \
    --cc=linux-mips@oss.sgi.com \
    --cc=pavel@suse.cz \
    --cc=shane@minirl.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