Re: Building gcc for an os less system

["Kai Ruottu" <karuottu at mbnet dot fi>]

<vishu27@cox.net> wrote:

> But now I get the following errors:
> 
> /tmp/ccAevql2.s:13352: Error: branch out of range
> /tmp/ccAevql2.s:14250: Warning: Failed to find real start of function: __ZNSt12strstreambufD1Ev
> 
> /tmp/ccAevql2.s:14250: Warning: Failed to find real start of function: __ZNSt9strstreamD0Ev
> 
> /tmp/ccAevql2.s:13514: Error: branch out of range
> make[7]: Leaving directory `/nfs/iadusr02/vsankara/xscale-gnu/build-gcc/xscale-coff/thumb/libstdc++-v3/src'

 Where on earth this 'xscale-coff' appeared from when you configured your toolchain for
'xscale-elf' :
 
> This is the command line I used to build gcc for c++ support
> 
> ../gcc-3.1/configure --target=xscale-elf --prefix=<bin-directory/xscale-elf --enable-languages=c,c++ --with-local-prefix=<bin-directory>/xscale-elf/xscale-elf
> 
> Please let me know how to get this fixed. I would really appreciate any help.

 Probably the 'xscale-coff' support is now seriously broken...  One difference between
the COFF and ELF object formats I remember is that the section names are restricted
to 8 characters (from 'include/coff/internal.h' in binutils, gdb etc.) :

	/********************** SECTION HEADER **********************/

	#define SCNNMLEN (8)

	struct internal_scnhdr
	{
	  char s_name[SCNNMLEN];        /* section name                 */


Things like this usually cause people to prefer ELF if the choice is free...  Maybe things
like this in COFF has been forgotten and the mangled C++ names do not fit into
something... I remember reports about some '-coff' target being broken, but maybe it
was 'sh-coff', 'mips-ecoff', 'm68k-coff', not 'arm-coff' or 'xscale-coff'...
 
 Anyway please try to find out how you suddenly were using '-coff' instead of the original
'-elf'....

Cheers, Kai
 


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com