Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pete Popov <ppopov@pacbell.net>
To: Marc Karasek <marc_karasek@ivivity.com>
Cc: "'linux-mips@oss.sgi.com'" <linux-mips@oss.sgi.com>
Subject: Re: MIPS Cross Compiler Tools
Date: Tue, 10 Jul 2001 10:55:53 -0700	[thread overview]
Message-ID: <3B4B41A9.3010304@pacbell.net> (raw)
In-Reply-To: 994784982.9191.1.camel@localhost.localdomain

Marc Karasek wrote:

> Will these be in the form of rpms or tgz files??  


rpm

In the case of rpm do
> you know if they would be package similar to the ones on oss.sgi.com?


I'm not sure how the oss.sgi.com tools are packaged. The MontaVista 
release gets installed in /opt/hardhat/<....>. The 
/opt/hardhat/devkit/mips/fp<le|be>/target is the root fs that gets 
mounted over nfs. The target root fs has all the userland apps and 
native tools. The /opt/hardhat/devkit/mips/fp_<le|be>/bin has the cross 
tools.


> ie Setup for a crossdev enviroment.  I just really need the cross tools
> as the dev is on an embedded system, with no harddrive.  


That's what we work with mostly as well.

> The userland
> stuff is pretty worthless to me.  I will be using busybox, tinylogin,
> etc. for the standard bin utilities.  


OK, but we have all of those packaged in rpm as well, and it's very easy 
to rebuild the rpms from the source rpms, if you need to rebuild them.

Pete

> Having a few megabytes to store
> everything in makes you very sensitive to size.... :-)
> 
> Thanks for the quick response...    
> 
> On 10 Jul 2001 09:39:02 -0700, Pete Popov wrote:
> 
>>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. 
>>>
>>Friday or Monday MontaVista should have the HHL2.0 Journeyman mips 
>>release on the ftp site which will include the userland apps, cross AND 
>>native tools, etc.  The tools and glibc are very up to date. I would 
>>suggest checking Monday for the release and using that instead of 
>>building your own.
>>
>>Pete
>>
> --
> /*************************
> 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:57 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 [this message]
2001-07-10 16:46 ` H . J . Lu
2001-07-10 17:05   ` Marc Karasek
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=3B4B41A9.3010304@pacbell.net \
    --to=ppopov@pacbell.net \
    --cc=linux-mips@oss.sgi.com \
    --cc=marc_karasek@ivivity.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