U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] is there any other toolchains for u-boot of mips arch?
Date: Tue, 22 Nov 2005 22:45:19 -0700	[thread overview]
Message-ID: <438401EF.20009@secretlab.ca> (raw)
In-Reply-To: <50c9a2250511222131qc5431cax9ab547e92918fb8d@mail.gmail.com>

Some quick etiquette points if your going to use the mailing list:
1. Put your replies *below* what your replying to, not above.
2. Always CC the mailing list on replies
3. Don't just describe what you saw; attach logs also.

zhuzhenhua wrote:
> i do not get clear about it
> $ export PATH=/path/to/mips-linux-as/bin:$PATH
> 
> /path/to/mips-linux-as/bin is what path?
If mips-linux-as is in the path /opt/mips-linux/bin, then:
$ export PATH=/opt/mips-linux/bin:$PATH

Basically, your tools should be in your path so you can run the tools
from the command line like this:
$ mips-linux-as

> 
> do you mean change my toolchain dir name to mips-linux-as?
I think your confused.  What is the full path of your cross compiler?

Here's an example:
My cross toolchain is: powerpc-linux
It lives in: /opt/powerpc-linux
The path to the cross gcc is: /opt/powerpc-linux/bin/powerpc-linux-gcc

Therefore I set in my environment:
$ PATH=/opt/powerpc-linux/bin:$PATH
$ CROSS_COMPILE=powerpc-linux-
$ export PATH CROSS_COMPILE

  parent reply	other threads:[~2005-11-23  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  1:28 [U-Boot-Users] is there any other toolchains for u-boot of mips arch? zhuzhenhua
2005-11-23  3:35 ` Grant Likely
     [not found]   ` <50c9a2250511222131qc5431cax9ab547e92918fb8d@mail.gmail.com>
2005-11-23  5:45     ` Grant Likely [this message]
2005-11-23 10:25       ` Anders Larsen
2005-11-23  7:46 ` Wolfgang Denk

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=438401EF.20009@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=u-boot@lists.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