Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: rolf liu <rolfliu@gmail.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linux-mips@linux-mips.org
Subject: Re: glibc based toolchain for mips
Date: Fri, 1 Jul 2005 16:09:26 -0700	[thread overview]
Message-ID: <2db32b7205070116091240fcf4@mail.gmail.com> (raw)
In-Reply-To: <20050701230056.D09EC353A36@atlas.denx.de>

Sorry I didn't say it clearly.

The files in /opt/eldk/mips_4KCle are in little endian mips, for sure. 
What I want is a cross-development tools for i386-to-mipsel, including
the corss gcc, binutils, other libs. I couldn't find such tools :(

thanks



On 7/1/05, Wolfgang Denk <wd@denx.de> wrote:
> In message <2db32b72050630155831582cd7@mail.gmail.com> you wrote:
> >
> > I download the package. after installation,  the 4KCle is still
> > linking to the mips-linux-, which is big-endian.
> 
> Please explain exactly what you did.
> 
> We have kernel, all libraries and apps running in  this  environment,
> and if I check it looks very much like little endinan, for example:
> 
> $ file /opt/eldk/mips_4KCle/bin/bash
> /opt/eldk/3.1.1/mips_4KCle/bin/bash: ELF 32-bit LSB executable, MIPS, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped
> 
> versus
> 
> $ file /opt/eldk/mips_4KC/bin/bash
>  /opt/eldk/3.1.1/mips_4KC/bin/bash: ELF 32-bit MSB executable, MIPS, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), stripped
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> CONSUMER NOTICE:  Because  of  the  "Uncertainty  Principle,"  It  Is
> Impossible  for  the  Consumer  to  Find  Out  at  the Same Time Both
> Precisely Where This Product Is and How Fast It Is Moving.
> 
>

  reply	other threads:[~2005-07-01 23:09 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
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 [this message]
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=2db32b7205070116091240fcf4@mail.gmail.com \
    --to=rolfliu@gmail.com \
    --cc=linux-mips@linux-mips.org \
    --cc=wd@denx.de \
    /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