All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Wu Qingbo <wu_qingbo2000@yahoo.com.cn>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: where can I get cross compiler and glibc for mipsel linux
Date: Mon, 7 Jan 2002 08:55:54 -0800	[thread overview]
Message-ID: <20020107085554.B2284@lucon.org> (raw)
In-Reply-To: <200201071019.g07AJZg31103@oss.sgi.com>; from wu_qingbo2000@yahoo.com.cn on Mon, Jan 07, 2002 at 05:20:25PM +0800

On Mon, Jan 07, 2002 at 05:20:25PM +0800, Wu Qingbo wrote:
> Hi, all,
> 
> I want to install cross compiler on my X86 linux system for mipsel linux.
> Where can I get them? And how to install them?
> Thanks in advance!
> 

You can try my RedHat 7.1.


H.J.
----
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 may 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.
4. baseline.tar.bz2 contains the cross build tree.
5. Since everything is cross compiled from x86, which is little endian,
many data files for mips, which is big endian, are either missing or
wrong. To get those data files for mips, you have to rebuild/install
the folowing rpms:

cracklib
glibc

natively on Linux/mips.

Thanks.


H.J.

  reply	other threads:[~2002-01-07 17:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07  9:20 where can I get cross compiler and glibc for mipsel linux Wu Qingbo
2002-01-07 16:55 ` H . J . Lu [this message]
2002-01-07 19:16 ` Jun Sun

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=20020107085554.B2284@lucon.org \
    --to=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=wu_qingbo2000@yahoo.com.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.