cross-compilation documentation

[Daniel Jacobowitz]

On Sun, Jun 22, 2003 at 03:36:07PM -0400, Peter Barada wrote:
> 
> >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.
> 
> All this talk is aboutn trying to get a 'bootstrap' compiler useful to
> build glibc.  Once glibc is build, the standard cross-compiler build
> method is to go back and build up a complete compiler(that includes
> the unwind stuff). So not having the unwind library shouldn't impose
> any problems on *building* glibc.  Running glibc is another matter.
> 
> What am I missing here?

Unless the code ends up _included_ in glibc.

Or in any of the dozens of little applications built at the same time
as glibc, for instance.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer