Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Marc Karasek <marc_karasek@ivivity.com>
To: Dan Temple <dant@mips.com>
Cc: Linux MIPS <linux-mips@oss.sgi.com>
Subject: Re: BE Toolchain
Date: 13 Nov 2001 09:49:20 -0500	[thread overview]
Message-ID: <1005662974.10352.2.camel@localhost.localdomain> (raw)
In-Reply-To: <3BE2A852.AFF0D905@mips.com>

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?

On Fri, 2001-11-02 at 09:06, Dan Temple wrote:
> Marc Karasek wrote:
> > 
> > Has anyone got the toolchain (binutils, gcc, glibc) to compile under
> > BE?  I followed the instructions at Bradley D. LaRonde has put together
> > and got the LE to work w/o a prolem.  I then proceeded to try the BE.
> > Binutils compiled ok, gcc says that mipseb-linux is not a valid target.
> > Looking in config.sub I saw a mips-linux, is this the BE option?
> 
> If you can wait a day, here's what we use - which is compilable both BE and LE:
> 
> We are going to release a complete RH7.1/MIPS installation image for the Atlas/Malta board on our FTP site, identical to what we use in MIPS engineering.All of our compiles for Linux/MIPS (except the kernel, which is probably irrelevant here) are done natively on Malta boards running Linux. We are using the compiler from the RedHat 7.1/MIPS Linux distribution. 
> 
> The toolchains on this distribution are (all commands run natively on
> the installation on a Malta board):
> 
> > uname -a
> Linux copmld07.mips.com 2.4.3-MIPS-01.02
> 
> > gcc -v
> Reading specs from /usr/lib/gcc-lib/mipsel-redhat-linux/2.96/specs
> gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-99.1)
> 
> > rpm -qf /usr/bin/ld
> binutils-2.11.92.0.10-1
> 
> > rpm -qa | grep glibc
> glibc-2.2.4-19.4
> glibc-common-2.2.4-19.4
> glibc-devel-2.2.4-19.4
> glibc-profile-2.2.4-19.4
>  
>   Dan Temple
>   MIPS Denmark
-- 
/*************************
Marc Karasek
Sr. Firmware Engineer
iVivity Inc.
marc_karasek@ivivity.com
(770) 986-8925
(770) 986-8926 Fax
*************************/

  parent reply	other threads:[~2001-11-13 14:48 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 [this message]
2001-11-13 15:55     ` H . J . Lu
2001-11-13 16:17       ` Marc Karasek
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=1005662974.10352.2.camel@localhost.localdomain \
    --to=marc_karasek@ivivity.com \
    --cc=dant@mips.com \
    --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