Re: help building gcc 3.2

["Ralph Blach" <rcblach at us dot ibm dot com>]

Rup,

No, I had to copy crti.o and libc.a to my gcc directory to get gcc to
compile.

Agreed that crti will be written in assembler, but libc.a will be written
in C and one would need the compiler
to compile it.  It seems like a chicken and egg issue.

Chip


Rupert Wood <rup@kanat.pair.com> on 10/09/2002 01:08:53 PM

To:    Ralph Blach/Raleigh/IBM@IBMUS
cc:    gcc-help@gcc.gnu.org
Subject:    Re: help building gcc 3.2



Ralph Blach wrote:

> I understand that these files are needed to link with, but thats for
> ld, not GCC the compiller.

OK, but the gcc binary is really just the compiler driver. It wraps
invocation of the proper backend compilers (cc1, cc1plus, f771, etc.
depending on language), the assember *and* the linker. (And, where
required, the collect2 pass.) When you're devloping with gcc - or any
other unix compiler I've seen - you almost never run ld yourself.

> The compiler really should not have to understand crti.o or any
> libraries to compile an source into an object.

No, it doesn't. And what did get successfully built in your build tree
should do just that.

Rup.