This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: build failure, GMP not available
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: Paul Brook <paul at codesourcery dot com>
- Cc: gcc at gcc dot gnu dot org, Ian Lance Taylor <iant at google dot com>, Mark Mitchell <mark at codesourcery dot com>, "Kaveh R. GHAZI" <ghazi at caip dot rutgers dot edu>, Geoffrey Keating <geoffk at apple dot com>
- Date: Wed, 01 Nov 2006 02:08:28 -0300
- Subject: Re: build failure, GMP not available
- References: <76B13B3C-DB38-4D40-9DEE-B1ADC71379FC@apple.com> <4546E82B.2080703@codesourcery.com> <m3wt6h7z2c.fsf@dhcp-172-18-118-195.corp.google.com> <200610311623.58024.paul@codesourcery.com>
On Oct 31, 2006, Paul Brook <paul@codesourcery.com> wrote:
> In my experience the first thing you do bringing up a new system is build a
> cross compiler and use that to build glibc and coreutils/busybox. This is all
> done on an established host that has gmp/mpfr ported to it.
> Bootstrapping a native compiler comes quite late in system bringup, and only
> happens at all on server/workstation-class hardware.
But then, for those, if you want to make sure you got a reproducible
build, you'll want to cross-build gmp and mpfr, cross-build a native
toolchain, bootstrap it, build gmp and mpfr with it and then bootstrap
again.
It would be *so* much nicer if one could just drop gmp and mpfr into
the GCC source tree and we'd use it during bootstrap.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}