linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ilya Gindentuller" <igin@vrcomm.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: What are the best cross-development tools to build Linux for MPC860, kernel ver. 2.2.13 or later?
Date: Thu, 9 Dec 1999 11:00:25 -0800	[thread overview]
Message-ID: <000901bf4277$a7c043c0$65daa8c0@vrcomm.com> (raw)


Hi, everybody!

We are complete novices in Linux development and want to learn how to use
Linux on MPC860.
So, please help us out since we are stuck with so many choices and versions
floating around.

I found Linux port for MPC860 ver.2.2.13 (in the ftp section of
www.ppc.kernel.org) and I want
to build it (as is) to run on our EST board.

We have to do cross-development under Windows 98/NT.
I searched mailing lists and it looks that everybody is using native Linux
(MAC) machines
to do development - no cross-development environment.

Please, could somebody direct us to the best source of embedded Linux
cross-development tools that we
can use on Windows 98/NT x86 machine to generate code for MPC860 EST board?

All input and instructions are welcome and greatly appreciated.

Thanks in advance,
                                Ilya Gindentuller


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-12-09 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-09 19:00 Ilya Gindentuller [this message]
1999-12-09 15:23 ` What are the best cross-development tools to build Linux for MPC860, kernel ver. 2.2.13 or later? Jim Chapman
1999-12-09 19:22 ` Grant Erickson

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='000901bf4277$a7c043c0$65daa8c0@vrcomm.com' \
    --to=igin@vrcomm.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).