Re: documentation for cross compiling.

["H . J . Lu" <hjl at lucon dot org>]

On Tue, Jul 03, 2001 at 01:23:20PM -0700, Daniel Jacobowitz wrote:
> > > That depends if you insist on full proper bootstraps or not.  Every
> > > time I to a daily build for one of our architectures, we start without
> > > a target libc installed.  This prevents all sorts of unpleasant
> > > lingering problems.
> > 
> > Check out my mips toolchain source rpm to see how I do it. I have a
> > setup to rebuild my Linux/mips from scratch. It is kind of tricky.
> 
> I have a perfectly working setup to do this.  It relies on the ability
> to build a minimal gcc for only C support without the presence of a
> target libc.  I consider that a perfectly reasonable requirement; don't
> you?

I don't think it is necessary. Bootstrap glibc/gcc for the very first
time is always a special case. I don't think you can automate it.
After that, you just need the appropriate glibc header files and
binary files to get a correct cross compiler, including C and C++.
You don't have to use any initial target binaries in the cross
toolchain to cross compile binaries for your target machine. At least,
that is how I do it. It is kind of tricky to do.

> 
> I've actually got a couple other patches floating around necessary for
> this, mostly to fix problems introduced in the DWARF2 unwinder.

I am very interested in them. I saw some gcc 3.0 C++ EH bug reports on
Linux/mipsel which I cannot duplicate with my 2.96 based toolchain.


H.J.