From: Andrew Lunn <andrew@lunn.ch>
To: "Moussa A. Ba" <mba@embedded-zone.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Recommended Version of GCC
Date: Thu, 11 May 2006 16:47:00 -0000 [thread overview]
Message-ID: <20060511164658.GJ11815@lunn.ch> (raw)
In-Reply-To: <44636666.7030600@embedded-zone.com>
On Thu, May 11, 2006 at 12:29:26PM -0400, Moussa A. Ba wrote:
> I am about to port ecos to an Oki eval board, ARM7TDMI, which version of
> GCC do you recommend I use. Should I just use the one distributed from
> the stable ecos release or can I use a more recent version from
> www.gnuarm.com or codesourcery.com
The version you can download from the eCos site is known to work
well. All the eCos tests have been carried out with it.
Newer verrsions of gcc have not been tested in the same way. However
users do use the newer versions of gcc and have not reported problems.
So the choice is yours.....
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-05-11 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 16:31 Moussa A. Ba
2006-05-11 16:47 ` Andrew Lunn [this message]
2006-05-12 9:10 ` Birahim Larou Fall
2006-05-12 16:53 Jay Foster
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=20060511164658.GJ11815@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mba@embedded-zone.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).