Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: David Christensen <dpchrist@holgerdanske.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Fw: hello
Date: Wed, 20 Mar 2002 09:38:42 -0800	[thread overview]
Message-ID: <20020320093842.B7190@dea.linux-mips.net> (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:

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

While it can be done there is not much point in doing so unless you hate
performance ;)

> > and native compile for apps.
> 
> OK  that sounds like a safe bet.

Which is the primary reason for native compiles.

> >> 3.  What is the preferred toolchain...
> > This is what we use for cross Kernel compiles (toolchain from oss):
> >
> > /home/hartvige> gcc -v
> > Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
> > gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)
> 
> Hmmm.  That looks like a native i386 compiler.  I'm surprised its not
> something like "mips-elf-gcc".

Yes, that's his native compiler.  mips-elf-gcc however should not be used,
there are subtle differences between the various ELF/MIPS targets that
would turn your life into hell ...

> I'll assume the cross-compile toolchain was built per
> http://oss.sgi.com/mips/mips-howto.html section 10.

That's roughly the procedure, though the procedure described is not 100%
suitable for the recommended compiler version.  So I recommend downloading
the binary rpms.

> 
> Leo Przybylski <leop@engr.arizona.edu> wrote:
> > Well, all Linux/MIPS stuff on on oss.sgi.com is maintained largely by
> > Ralf Baechle who is also contributor to numerous Linux/MIPS projects
> > on sourceforge. As far as I know he is also a huge part of the
> > sourceforge Linux/MIPS. You may have noticed that Bradley D. LaRonde
> > is also a huge contributor.

No.  I don't touch or follow the Sourceforge project at all.

  Ralf

      parent reply	other threads:[~2002-03-20 17:37 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
2002-03-20  8:59 ` Hartvig Ekner
2002-03-20  8:59   ` Hartvig Ekner
2002-03-20 17:38 ` Ralf Baechle [this message]

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=20020320093842.B7190@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --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