From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: laurent.pinchart@capflow.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Development tools version
Date: Thu, 28 Feb 2002 14:24:35 +0000 [thread overview]
Message-ID: <3C7E3DA3.9010800@cambridgebroadband.com> (raw)
In-Reply-To: 3C7E3471.4080708@capflow.com
Laurent,
We're also use the MPC860. For the tools we use CDK 2.0 from Montavista, and we've had no problems
with this. To install CDK 2.0 for the 860 do this:
> cd /mnt/cdrom/bin
> ./hhl-host-install
... and then select "embeddedplanet-rpxlite" for the board
This provides you with:
i) libraries
ii) a root filesystem for NFS mounting your target
iii) standard tools ppc_8xx-gcc, ppc_8xx-ld, etc.
After this installation all you need to do to compile a linuxppc kernel is change CROSS_COMPILE to
ppc_8xx- in the top level Makefile.
Alex
Laurent Pinchart wrote:
>
> Hi everybody.
>
> I searched the web for some information about this, but haven't been
> able to find any answer to my question.
>
> I'd appreciate if someone could give me an advice about which version of
> the different development tools (namely binutils & gcc), and which
> version of the C library (either glibc or newlib) I should use for a
> MPC860T processor.
>
> I currently use the Hard Hat Journeyman Edition (and recompiled
> everything from the rpm sources), but was wondering if it would be
> better to stick with it or use a newer version of some tools.
>
> I suppose that GCC 3.x is not ready for the MPC8xx yet (but I might be
> wrong).
>
> Thanks in advance for your help.
>
> Laurent Pinchart.
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-28 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 13:45 Development tools version Laurent Pinchart
2002-02-28 14:24 ` Alex Zeffertt [this message]
[not found] ` <3C7E372A.7B4E5F0@lvl7.com>
[not found] ` <3C7F3507.1060702@capflow.com>
2002-03-01 11:30 ` Neil Horman
2002-03-01 12:24 ` Magnus Damm
2002-03-01 12:32 ` Neil Horman
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=3C7E3DA3.9010800@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=laurent.pinchart@capflow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.