+++ Andrew Stubbs [2010-10-07 12:46 +0100]: > On 07/10/10 12:03, Wookey wrote: > A possible solution to the problem would be to include the sources to > libgcc.a in the installation, and teach gcc to compile it on-the-fly, as > necessary.
If it was possible to separate-out libgcc somewhat so that it could be built outside the whole compiler build, that would be marvelous, but my (vague) understanding of the way things are done was that this was not really practical. Is it? And whilst on the subject - do the other libs like gomp mudflap and erm <any others> that come of of toolchain builds need to be built in the same set of flavours or is this issue restricted to libgcc? Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
