This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Recommended gcc version for 1.0?
Grant Edwards <grante@visi.com> writes:
> On Wed, Aug 06, 2003 at 04:18:22PM +0100, Nick Garnett wrote:
>
> > > When did big-endian ARM gcc users become second-class citizens?
> > > I swear that for 2.95, doing a "confgure --target=arm-elf" used
> > > to work just fine.
> >
> > 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:
>
> $ rpm -q -l arm-elf-gcc | grep '\.a'
> /usr/local/lib/gcc-lib/arm-elf/2.95.2/be/libgcc.a
> /usr/local/lib/gcc-lib/arm-elf/2.95.2/be/nofmult/libgcc.a
> /usr/local/lib/gcc-lib/arm-elf/2.95.2/libgcc.a
> /usr/local/lib/gcc-lib/arm-elf/2.95.2/nofmult/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:
./thumb/interwork/xscale/libgcc.a
./thumb/interwork/libgcc.a
./thumb/interwork/armv4t/libgcc.a
./thumb/libgcc.a
./thumb/xscale/libgcc.a
./thumb/armv4t/libgcc.a
./libgcc.a
./interwork/xscale/libgcc.a
./interwork/libgcc.a
./interwork/armv4t/libgcc.a
./xscale/libgcc.a
./strongarm/libgcc.a
./armv4t/libgcc.a
With associated crt0.o etc for each. BE would double that to 26.
> However, building those files didn't take a noticable amount of
> time. When I built 3.2.1, it looked like it spent most of its
> time building general libc and libm type stuff. Doesn't eCos
> provides it's own libc and libm libraries?
I think part of the problem is that it is hard to avoid building those
libc/libm libraries too. We also didn't have an infinite amount of
time in which to build all the toolchains we needed.
> > At least that is my understanding. I expect a toolchain expert
> > will be along in a minute to provide any corrections.
I'm at the limit of my knowledge here. I'm probably talking complete
rubbish.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss