cross-compilation documentation

[Zack Weinberg]

Dan Kegel <dank@kegel.com> writes:

> Zack Weinberg wrote:
>> Andrew Pinski <pinskia@physics.uc.edu> writes:
>>>RCS file: /cvs/gcc/gcc/gcc/config/rs6000/linux.h,v
>>> -#ifdef IN_LIBGCC2
>>>+#if defined (IN_LIBGCC2) && !defined (inhibit_libc)
>>> #include <signal.h>
>>> ...
>> For what it's worth, that looks like the right fix to this immediate
>> problem.  We want to decouple libgcc build from compiler build for
>> other reasons, but that's sufficiently invasive that it's probably a
>> 3.5 item at this point (the way I wanna do it, it needs bootstrap to
>> run at top level, and it involves moving a lot of files).
>
> If this is the right way to go, then you need to patch
> not just rs6000, but also just about every other architecture,
> don't you?

Yes, probably.  But Dan raises a valid point.  I wonder if it would
make sense to disable the unwind library entirely when inhibit_libc 
is true.  The trouble with that is I don't know what unwind-related
things are lurking in corners of glibc.

zw