Basic build questions

[Mike Stump]

> From: "Bates, Rod" <Rod.Bates@Wichita.BOEING.com>
> To: "'egcs@egcs.cygnus.com'" <egcs@egcs.cygnus.com>
> Date: Thu, 24 Jun 1999 12:48:47 -0500

> mrs@wrs.com answered me: 

> >> 1) Is it true that, during the second build of the compiler, I must
> >> be able to get xgcc to link *.o files which it built with *.o and
> >> *.a file(s) that are provided by the native OS?  In particular,
> >> probably crt*.o and libc.a?  Trying to do this is where the
> >> incompatibilities show up.
> >
> >No.  You can cross compile from anything, and provide your own libc.a
> >built with the GNU tools, if you want.  If you want to use the native
> >libc.a, then you will have to find a way to convert them, or otherwise
> >make things compatible.

> So, let me refine my question.  Using the normal native compiler
> build process, (i.e. not the cross compiler process), is it true
> that I must be able to get xgcc to link *.o files which it built
> with *.o and *.a file(s) that are provided by the native OS?

No.  You can still build a libc and various startup file yourself, but
you have to have them...  If you don't, then if you want to use them,
you will have to either convert them, or make the GNU tools otherwise
compatible with them.

> I think your answer to this is "yes", and that I will have to build
> a cross compiler on another machine, use it to cross compile libc
> etc., put the results on the target machine, and then build from
> there.  Is this right?

The first part, no, the second part, yes, you can do this, but you
don't have to.