Trouble building 4.4.2 cross compiler for arm-elf target

Thomas Martitz thomas.martitz@student.HTW-Berlin.de
Thu Nov 19 15:29:00 GMT 2009


Am 19.11.2009 16:26, schrieb Kai Ruottu:
> Kai Ruottu wrote:
>> Ok, if one needs ONLY GCC, then the make command is :
>>
>>   make all-gcc
>>
>> and the install command is :
>>
>>   make install-gcc
>>
>> If these command succeed, then you really haven't understood 
>> something very
>> basic in GCC :(  It is only a collection of compilers!  But the GCC 
>> sources will
>> include all kind of extra stuff which will be tried to be built too: 
>> 'libgcc' (earlier
>> even the 'make all-gcc' tried to produce it), 'libstdc++', 
>> 'libjava',....
> Some time in the past, maybe it was gcc-2.8.x, the GCC sources 
> included only
> GCC and libgcc sources, in 'gcc'.  Nowadays the C++ classes are included,
> libiberty too,  all kind of extra stuff which some may consider as 
> "rubbish" or
> "spam" :)  Maybe the standard C library comes next, even now quite many
> seem to suggest in the net that it is "obligatory" to build glibc with 
> a cross GCC!
>
> So it may sound frustrating when 'make' doesn't try to produce ONLY the
> compilers (no target stuff outside the GCC sources will be required 
> for that).
> The 'make all-gcc' and 'make install-gcc' however have been there very 
> long
> so maybe there is some attitude that "everyone knows them already" and 
> the
> GCC docs don't tell about this "only GCC binaries wished" case :(
>


Please send messages to the mailing list instead of to me privately.

So, does make all-gcc build libgcc.a?

Best regards.



More information about the Gcc-help mailing list