linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Is GCC >= 3.1 available for ELDK ? (or other means to compile Ada code)
Date: 06 Jun 2003 13:34:00 +0200	[thread overview]
Message-ID: <87el27wic7.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: 30C145E544071F4FB8B627789F7910BD328FEE@csy-exchange1.giat.intra


Hello Albert,

> Here at work I've been asked to get some Ada code ported on an
> embedded, MPC855T-based platform using ELDK 2.02.
>
> By the look of it, there are no major risks with repsect to the
> scheduler or libraries or performance; the only problem is getting
> to compile Ada code.
>
> GCC supports Ada from version 3.1.1 up, but ELDK 2.0.2 features 2.95.4.
>
> Is there a version of GCC >= 3.1.1 prepackaged for ELDK?

Short answer - no.

The ELDK still contains the reliable 2.95.4 compiler + associated
binutils because there were several problems with the >=3.0 toolchains
on the ppc platform.  To check the situation, I recently compiled gcc
3.2.2 + binutils 2.13 as a cross-compiler for the 8xx platform without
major problems out of the box.  A linux kernel compiled with the setup
ran with no noticeable difficulties so I am pretty confident that
the setup is stable for that platform.

The only reason that there is no pre-packaged gcc >= 3.1 for the ELDK
is the well known 24h/day limit and the fact that no customer demanded
a newer gcc as yet.

Hope that helps
  Detlev

--
Spelling is a lossed art


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

  reply	other threads:[~2003-06-06 11:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06  8:56 Is GCC >= 3.1 available for ELDK ? (or other means to compile Ada code) ARIBAUD Albert
2003-06-06 11:34 ` Detlev Zundel [this message]
2003-06-18 17:04   ` John Zhou
2003-06-18 18:04     ` Conn Clark
2003-06-18 18:56     ` 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=87el27wic7.fsf@deepthought.outer.space.org \
    --to=dzu@denx.de \
    --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).