This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Recommended gcc version for 1.0?


On Wed, Aug 06, 2003 at 07:00:12PM +0100, Nick Garnett wrote:

> > > This was done to keep the number of different versions of the
> > > libraries down.
> > 
> > Here is where I get confused.
> > 
> > What libraries?
> > 
> > When I build 2.95.2 for use with eCos, the only library that is
> > built is libgcc.a:
[...]
> > Eliminating big-endian would cut that from four files to two.
> > 
> > There are now 21 different libgcc.a files in my 3.2.1
> > toolchain. Big endian support constitutes 8 of those files.
> 
> Well, in the toolchain I have, I see under lib/gcc-lib/arm-elf/3.2.1:
>
[13 files]
> With associated crt0.o etc for each. BE would double that to 26.

It adds 8, resulting in a total of 21.

Of the non-libgcc.a files (126 total) BE appears to be
responsible for 48 of them.

> I think part of the problem is that it is hard to avoid building those
> libc/libm libraries too.

I see. Apparently that's something that happened since 2.95,
since it didn't used to be necessary to build them.

-- 
Grant Edwards
grante@visi.com

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]