This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Re: eCos tools' gcc minor version
- From: "Sam Sortais" <sams at myself dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Thu, 14 Feb 2002 02:40:51 +0800
- Subject: Re: [ECOS] Re: eCos tools' gcc minor version
This brings some questions in my mind.
I do not understand what the current patch to
gcc2.95 is doing and if it is to solve a general compiler problem or a specific patch to get eCos working only.
More generally I am wondering if next compiler
version will need to be patched to work with
eCos.
And my main issue is to find out if I could use
the same compiler to build some objects for Linux and eCos target in case this object/libraries have nothing to do with the underlying OS.
I would like to avoid to recompile everything
whether I am compiling for Linux, eCos or eCos synthetic target.
Thanks,
Sam.
--
Robin Farine wrote:
>
> Ah, now it becomes a little clearer. So this Cygnus gcc version
> corresponds more or less to egcs-1.1.1 (wich became gcc-2.9[01])?
In terms of features it's clearer to 2.95. It was branched about when 2.95
was branched to be stabilised.
> For an StrongARM target, may I safely use the vanilla gcc-2.95.3 patched
> with ecos-gcc-2952.patch from the Red Hat website (the reload1.c chunk
> removed since it seems 2.95.3 includes a fix for this), or should I
> better use a pre-2.95.4 CVS snapshot?
For strongarm you probably don't need a patch at all.
One of things I'll be doing as part of (or at least immediately after) v2
is released is updating all the instructions for 3.0.
Jifl
--
_______________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Win a ski trip!
http://www.nowcode.com/register.asp?affiliate=1net2phone3a
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss