From: Marc Karasek <marc_karasek@ivivity.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: Dan Temple <dant@mips.com>, Linux MIPS <linux-mips@oss.sgi.com>
Subject: Re: BE Toolchain
Date: 13 Nov 2001 11:17:09 -0500 [thread overview]
Message-ID: <1005668252.19178.52.camel@localhost.localdomain> (raw)
In-Reply-To: <20011113075543.A30676@lucon.org>
I was refering to a formal (supported) release from RH. Something I can
pay RH to get support for.
On Tue, 2001-11-13 at 10:55, H . J . Lu wrote:
> On Tue, Nov 13, 2001 at 09:49:20AM -0500, Marc Karasek wrote:
> > I have one question: I did not know that RH had a MIPS dist for 7.1.
> > Is this something MIPS has done from the RH sources? Or is RH planning
> > on supporting MIPS now?
> >
>
> Red Hat doesn't have a mips port. It is me who ported RedHat 7.1 to
> mips.
>
>
> 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.
--
/*************************
Marc Karasek
Sr. Firmware Engineer
iVivity Inc.
marc_karasek@ivivity.com
(770) 986-8925
(770) 986-8926 Fax
*************************/
next prev parent reply other threads:[~2001-11-13 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 13:37 BE Toolchain Marc Karasek
2001-11-02 14:06 ` Dan Temple
2001-11-02 14:18 ` Marc Karasek
2001-11-02 15:36 ` H . J . Lu
2001-11-13 14:49 ` Marc Karasek
2001-11-13 15:55 ` H . J . Lu
2001-11-13 16:17 ` Marc Karasek [this message]
2001-11-13 16:30 ` H . J . Lu
2001-11-13 16:45 ` Alan Cox
2001-11-13 16:45 ` Alan Cox
2001-11-13 19:30 ` Pete Popov
2001-11-15 21:42 ` SGI harddisk only - Debian install Garrick Evans
2001-11-16 1:05 ` Garrick Evans
2001-11-02 15:49 ` BE Toolchain Bradley D. LaRonde
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=1005668252.19178.52.camel@localhost.localdomain \
--to=marc_karasek@ivivity.com \
--cc=dant@mips.com \
--cc=hjl@lucon.org \
--cc=linux-mips@oss.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