Re: question re gcc-runtime vs libgcc

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Sat, 2011-01-01 at 00:22 +1100, Angus Lees wrote:
> On Fri, Dec 31, 2010 at 23:46, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > gcc-runtime is build process for bits that can be built standalone like
> > libstdc++. For pieces of gcc that can't be built separately like libgcc,
> > we take a stashed version of it from gcc-cross and only package it as
> > part of gcc-runtime.
> 
> ok, but where should libgcc be during the linking of libstdc++?
> 
> As far as I can see, at this point in a clean build libgcc only exists
> in the temporary gcc-build-internal-* directory, which isn't in the
> gcc search path.  libgcc doesn't make it out into the sysroot until
> _after_ libstdc++, libssp, etc are built and gcc-runtime is installed.
>  Where should gcc-cross be finding libgcc when linking libstdc++ and
> friends?

This is a good point. Its finding the libgcc installed by
gcc-cross-intermediate. This happens to work out ok but its not a good
design.

We're currently working on various issues in the toolchain bootstrap
process, particularly to ensure that files don't get overwritten in
staging during the bootstrap process. Those changes should help solve
this particular problem too...

Cheers,

Richard