Re: [ECOS] The Nano Saga - Part the Third - libsupc++

[Martin Buck <martin dot buck at ascom dot ch>]

Warren Postma wrote:
> For reference, I configured/built GCC 3.2 thus:
> 
> mkdir -p /tmp/build/gcc
> cd /tmp/build/gcc
> /usr/src/gcc-3.2-1/configure \
>     --target=arm-elf \
>     --prefix=/tools \
>     --exec-prefix=/tools/H-i686-pc-cygwin \
>     --with-gnu-as \
>     --with-gnu-ld \
>     --with-newlib -v 2>&1 | \
>      tee /tmp/built/gcc/gcc-configure.out
> make -w all-gcc install-gcc LANGUAGES="c c++"
> 
> So next, I got newlib from cvs, but as I have no idea how to do the
> "symlink" stuff Jonathan mentions, like where to put it, and what to call
> it.

You don't have to do anything with it if you created the symlinks - the
gcc build will find it automatically and configure it for you. Creating
the symlinks is easy: If you unpacked newlib to /usr/src/newlib-1.10.0,
just run these commands:
ln -s /usr/src/newlib-1.10.0/newlib /usr/src/gcc-3.2.1
ln -s /usr/src/newlib-1.10.0/libgloss /usr/src/gcc-3.2.1

If you're using a different newlib version, you have adjust the
direcrtory names, of course.

And then you have to add "all-target-libstdc++-v3" and
"install-target-libstdc++-v3" to the make command line above so that
libsupc++.a really gets built and installed.

> So do I have to go back to GCC 2.x now or can anybody help me get GCC 3.2
> libsupc++ (newlib?) support so I can do the linkage of the eCos Tests to run
> on my target.

If you want to avoid all that trouble, the easiest way is still to use
the versions of gcc and binutils that are recommended on the eCos
website (unless your target is not supported by them, of course).
There's a reason why these are the recommended versions...

Good luck,
Martin

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