Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: "Fu, He Wei PSE NKG" <hewei.fu@siemens.com>
Cc: linux-mips@linux-mips.org
Subject: Re: The difference between mips*-gnu and mips*-linux when configure tool-chain
Date: Sun, 3 Dec 2006 12:05:15 -0500	[thread overview]
Message-ID: <20061203170514.GA11258@nevyn.them.org> (raw)
In-Reply-To: <96E7D5519FC3D741BEE27AB88C7387970162312C@PEKW934A.cn001.siemens.net>

On Sun, Dec 03, 2006 at 05:15:07PM +0800, Fu, He Wei PSE NKG wrote:
> Hello everyone.At the time of building tool-chain for mips machine,we
> can choose mips*-gnu or mips*-linux, I want to know what's the
> difference between them? The original idea is that mips*-gnu for
> developing firmware which has not OS-surport, and mips*-linux for
> developing software on Linux, but it is not suitable for firmware such
> as bootloaders.But now I think I'm not right,it seems that configure
> with mips*-linux suit for both linux and bootloader, and configure with
> mips*-gnu means build for OS such as IRIX surport, I'm not very
> clearly,can anybody help me figour out the difference between them?

mips-gnu is the GNU system (the Hurd kernel).  mips-linux is used for
the kernel and userspace of a Linux system.  mips-elf is used for bare
metal targets without an OS.

You should be able to build a Linux bootloader using a mips-linux
compiler.

-- 
Daniel Jacobowitz
CodeSourcery

  parent reply	other threads:[~2006-12-03 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03  9:15 The difference between mips*-gnu and mips*-linux when configure tool-chain Fu, He Wei PSE NKG
2006-12-03  9:15 ` Fu, He Wei PSE NKG
2006-12-03 17:05 ` Daniel Jacobowitz [this message]
2006-12-05  3:41   ` Fu, He Wei PSE NKG
2006-12-05  3:41     ` Fu, He Wei PSE NKG
2006-12-05 12:43     ` Thiemo Seufer

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=20061203170514.GA11258@nevyn.them.org \
    --to=dan@debian.org \
    --cc=hewei.fu@siemens.com \
    --cc=linux-mips@linux-mips.org \
    /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