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 02:31:48PM -0700, H . J . Lu wrote:
> 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.
But I disagree. Not only that, I disagree in code - I have automated
it, for MIPS, PowerPC, i386, ARM, and SH. It prevents vicious cycles
from a bad compiler being any concern. It means we don't have to have
part of yesterdays broken build lying around to contaminate today's
fixed one. I consider it vital.
> > 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.
They won't affect those. The only thing they're for is removing the
need to include, e.g., <signal.h> when building libgcc.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer