Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: rolf liu <rolfliu@gmail.com>
To: Andy Isaacson <adi@hexapodia.org>
Cc: Prashant Viswanathan <vprashant@echelon.com>, linux-mips@linux-mips.org
Subject: Re: glibc based toolchain for mips
Date: Fri, 24 Jun 2005 15:47:30 -0700	[thread overview]
Message-ID: <2db32b7205062415471d0fe4c0@mail.gmail.com> (raw)
In-Reply-To: <20050624223915.GB4295@hexapodia.org>

That one Debian provides is for big endian. Is there one tool chain
for mips little endian and also gcc 3.*.* ?


On 6/24/05, Andy Isaacson <adi@hexapodia.org> wrote:
> On Fri, Jun 24, 2005 at 03:14:49PM -0700, Prashant Viswanathan wrote:
> > Is it possible to get a free/open glibc based toolchain for MIPS? Buildroot
> > and ucLibc based toolchain seems to work well, but I really need a glibc
> > based toolchain. Though I can use the SDE from MIPS technologies to build
> > the kernel, I can't seem to use it as a toolchain to compile my own
> > applications.
> 
> Debian provides a complete native toolchain with glibc, which I've used
> with great success.  (You will need to do a nfsroot or nbd-root if you
> don't have local storage.)
> 
> -andy
> 
>

  reply	other threads:[~2005-06-24 22:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 22:14 glibc based toolchain for mips Prashant Viswanathan
2005-06-24 22:39 ` Andy Isaacson
2005-06-24 22:47   ` rolf liu [this message]
2005-06-24 23:10     ` Andy Isaacson
2005-06-24 23:35       ` rolf liu
2005-06-24 23:57         ` Andy Isaacson
2005-06-25  0:23     ` Wolfgang Denk
2005-06-30 22:58       ` rolf liu
2005-07-01 23:00         ` Wolfgang Denk
2005-07-01 23:09           ` rolf liu
2005-07-02 15:39             ` Wolfgang Denk
2005-06-26 10:22 ` TheNop
  -- strict thread matches above, loose matches on Subject: below --
2005-06-24 22:42 Prashant Viswanathan
2005-06-25  3:31 ` Kumba
2005-06-26  8:05   ` Geert Uytterhoeven

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=2db32b7205062415471d0fe4c0@mail.gmail.com \
    --to=rolfliu@gmail.com \
    --cc=adi@hexapodia.org \
    --cc=linux-mips@linux-mips.org \
    --cc=vprashant@echelon.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