[PATCH] Fix unified tree breakage

Alexandre Oliva aoliva@redhat.com
Fri Oct 7 09:14:00 GMT 2005

On Oct  5, 2005, Alexandre Oliva <aoliva@redhat.com> wrote:

> On Oct  5, 2005, Paolo Bonzini <paolo.bonzini@lu.unisi.ch> wrote:
>> In 4.2, we'll have *toplevel* bootstrap enabled by default.  This is
>> what you saw indicated as "@if gcc-bootstrap", and it means that the
>> toplevel orchestrates a 3-stage build of libiberty, binutils, and
>> everything else up to gcc.  In this case it will just work because
>> stage1 will use the system assembler/linker, and stage2/3 will use the
>> previous stage of the in-tree assembler/linker:

> This is not good.  It means the libgcc build uses one pair of
> assembler/linker different from the one that gets installed.  Each
> stage must use its own assembler/linker to build the GCC libraries.

And, just to clarify why it's so important to get this right, when
bootstrapping GCC, starting without GNU binutils, but configuring GCC
to use binutils, you'd likely get assembler/linker failures while
building libgcc for stage1.

Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

More information about the Newlib mailing list