Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Karsten Merker <karsten@excalibur.cologne.de>
To: David Christensen <dpchrist@holgerdanske.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Fw: hello
Date: Wed, 20 Mar 2002 07:39:27 +0100	[thread overview]
Message-ID: <20020320073927.A471@excalibur.cologne.de> (raw)
In-Reply-To: <017701c1cf99$a7d9a890$0b01a8c0@w2k30g>; from dpchrist@holgerdanske.com on Tue, Mar 19, 2002 at 02:55:22PM -0800

On Tue, Mar 19, 2002 at 02:55:22PM -0800, David Christensen wrote:

> Which Linux distribution does MIPS use?  Since I'm going to be working
> on an Atlas board using software from MIPS, I would like to match things
> up exactly.

Several different - there is a Debian port (big and little endian),
H.J. Lu's RedHat mini-port (big endian AFAIK), Karel van Houten's 
RedHat-based rootfs (little endian), Keith M. Wesolwski's Simple
Linux (big-endian). I think the most complete of all is Debian.

> As an aside, is anybody using a VMware virtual machine for their
> development host?

Why should we? VMware emulates i386 on i386, so it would be of no
help for mips development.

> >> 3.  What is the preferred toolchain...

I always build natively:
gcc version 2.95.4 20011002 (Debian prerelease)
GNU ld version 2.11.93.0.2 20020207 Debian/GNU Linux

> > Yep - The Debian autobuilder run native on little and big endian.
> 
> Hmmm.  Do you mean GNU autoconf running natively on MIPS, or something
> running on a Debian x86 host, or something else?

The autobuilder is a system that checks for new Debian packages which
are not yet built for mips/mipsel and automatically builds and uploads
them into the Debian archive. It runs natively (in our case on a
Lasat Masquerade Pro for little endian and on an SGI Indigo2 for big 
endian).

Regards,
Karsten
-- 
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.

  parent reply	other threads:[~2002-03-20  6:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19 22:55 Fw: hello David Christensen
2002-03-19 22:55 ` David Christensen
2002-03-20  6:39 ` Karsten Merker [this message]
2002-03-20  8:59 ` Hartvig Ekner
2002-03-20  8:59   ` Hartvig Ekner
2002-03-20 17:38 ` Ralf Baechle

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=20020320073927.A471@excalibur.cologne.de \
    --to=karsten@excalibur.cologne.de \
    --cc=dpchrist@holgerdanske.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