Re: [ECOS] [PATCH] Problem compiling host tools with different TCL version

["Greg Holdren" <greghol at sbcglobal dot net>]

>Also I'm going to build a new set of toolchains for a arm-elf (AEB-1). I
have
>a 2.95 set working but want to test 3.2 branch.
>Will I get any problems/improvements with 3.2 branch? Should I stick with
>2.95?
>Do I need to patch 3.2 gcc like old 2.95 instructions in ecos site?

Here is what I did to make arm-elf tools with gcc-322, binutils-2.13.2. My
target is the Atmel EB40.

You need to get newlib-1.11.0.tar.gz and unpack/build it to get around the
missing libsupc++.a otherwise you will get an error while trying to compile
the ecos code. Follow the directions in the message link below dealing with
the symlinks and replace with your real paths after unpacking
newlib-1.11.0.tar.gz.

http://sources.redhat.com/ml/ecos-discuss/2002-11/msg00042.html

Proceed like the ecos site shows. Build binutils. After running the
configuration script for gcc, do:

make -w all-target-libstdc++-v3  install-target-libstdc++-v3 LANGUAGES="c
c++" 2>&1 | tee make.out

I had to follow it up with...

make -w all-gcc install-gcc LANGUAGES="c c++" 2>&1 | tee make.out

....to get the compiler tools bits.

I guess they could be combined into one make line.

Proceed to insight-5.3.

Worked for me with my EB40 builds.

Greg



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