Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Marc Karasek <marc_karasek@ivivity.com>
To: H "." J "." Lu <hjl@lucon.org>
Cc: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: MIPS Cross Compiler Tools
Date: 10 Jul 2001 13:05:01 -0400	[thread overview]
Message-ID: <994784701.9191.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20010710094627.D19026@lucon.org>

This is for an embedded platform, with no harddrive.  So I will need to
use things like busybox, etc.  I just need the headers & libs.  So far I
have only been able to find glibc-2.2.2 from deb in an rpm format.
Could not get this to install in /usr/local/mips-linux/...  properly.  I
guess what I am really looking for is a tgz file of the libs/headers.
SO I can put it where I want it. Any packaged dist (RH, deb) would not
be usefull in this scenario.  At least that is my experience todate.... 

Thanks for the quick response..

On 10 Jul 2001 09:46:27 -0700, H . J . Lu wrote:
> On Tue, Jul 10, 2001 at 12:27:43PM -0400, Marc Karasek wrote:
> > I had a question about the cross compiler tools for MIPS, specifically
> > glibc.  I d/l the rpms from oss.sgi.com,  but they are only binutils, and
> > the compiler (C, C++).  
> > 
> > Are most people building glibc against these or are you building the tools
> > completely from scratch?  As glibc is needed to compile anything else other
> > than the kernel. 
> 
> My RedHat 7.1 release on oss.sgi.com has the complete cross toolchain:
> 
> 
> 
> 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.
> 2. You have to find a way to put those rpms on your machine. I use
> network boot and NFS root to do it.
--
/*************************
Marc Karasek
Sr. Firmware Engineer
iVivity Inc.
marc_karasek@ivivity.com
(770) 986-8925
(770) 986-8926 Fax
*************************/

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10 16:27 MIPS Cross Compiler Tools Marc Karasek
2001-07-10 16:35 ` Steve Langasek
2001-07-10 17:11   ` Marc Karasek
2001-07-10 16:39 ` Pete Popov
2001-07-10 17:09   ` Marc Karasek
2001-07-10 17:55     ` Pete Popov
2001-07-10 16:46 ` H . J . Lu
2001-07-10 17:05   ` Marc Karasek [this message]
2001-07-10 17:07     ` H . J . Lu
2001-07-11  8:41     ` Gleb O. Raiko

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=994784701.9191.0.camel@localhost.localdomain \
    --to=marc_karasek@ivivity.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