This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Is a target glibc really needed to build full crossgcc?


On 2005-09-14 at 16:58:13 Kai Ruottu wrote:

>> Yes, GCC's configure scripts can try to link against the library when
>> building other libraries as part of building GCC.

>   The produced 'libgcc_s.so's and 'libstdc++.so's are examples for these,
> producing shared libraries happens quite in the same way as producing
> executables.

Indeed, this is of course the reason that the "bootstrap" gcc is built
with --disable-shared.

So, to partially answer the original poster's question: yes, you could
build /only/ the bootstrap gcc, and have it work even without any
headers (just use --without-headers, or --with-newlib).  But this gcc
will not be able to output any executables or shared libraries, only
.s and .o files.


>   If enough people would believe that a cross-GCC really is aimed to
> be built in one stage after building the binutils and preinstalling
> the existing target C libraries, and would report any problems in
> this normal build type, the world would be much simpler and easier.

But what if you don't *have* any existing target C library?  Then you
will still need to build it yourself, somehow.  And that is done with
the bootstrap compiler.

Attachment: pgp00000.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]