This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: documentation for cross compiling.
On Tue, Jul 03, 2001 at 05:37:26AM -0700, Daniel Jacobowitz wrote:
> >
> > I have done that many times. It only happens once per port.
>
> 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.
>
> When I build gcc first for a given target, I have no libc.
>
> > > Actually, I have such a kind of experience for our GNU/Linux support
> > > of SuperH. The bootstrap goes like this.
> > >
> > (0) Install the header files from the x86 port.
>
> That's gross. I'm not amazed that it works, but if anything ever goes
That is how to start a new glibc port. At this point, you only want
ta gcc compiler for your new target. Those header files will be just
enough to finish the minimal gcc build. It is a very tricky thing to
do. Fortunately, I only need to do it once per target.
> wrong it'll be almost impossible to track down.
Can you guess I created the very first Linux cross toolchain more
than 10 years ago?
H.J.