Re: [avr32-libc-devel] Building AVR32-Libc with GNU tool chain

[Weddington, E. <Eri...@at...>]

 

> -----Original Message-----
> From: Kaushik, Praveen_Kumar [mailto:Pra...@at...] 
> Sent: Tuesday, July 20, 2010 6:11 AM
> To: avr...@li...
> Cc: Kaushik, Praveen_Kumar
> Subject: [avr32-libc-devel] Building AVR32-Libc with GNU tool chain
> 

> The option --with-newlib has still to be given while 
> configuring GCC because GCC's configure scripts recognize 
> this option in order to perform some checks which fail 
> otherwise due to absence of crt files at that time. 
> --with-newlib option eliminates the need for those checks 
> (this option does some more stuff, still exploring this). 
> 

Hi Praveen,

IIRC, the option --with-newlib is needed when building with Newlib because GCC requires some *header files* that Newlib provides when building the initial C compiler.

So, as I understand it, the build process is something like:

1. Build binutils (for assembler, linker, etc.)
2. Build GCC, C compiler only (use --with-newlib for certain header files)
3. Build Newlib, using the just built C compiler
4. Build GCC, full C compiler and C++ compiler (and whatever other languages are specified).

However, building for the AVR target avoid this. Building for the AVR is easier:

1. Build binutils
2. Build GCC (C, C++, or other specified languages)
3. Build avr-libc

So obviously there is some difference between the AVR and AVR32 targets here. I could be wrong about the --with-newlib switch being for certain header files. This needs to be investigated further.

But overall there might be a way to build the AVR32 toolchain like it is done for the AVR target. We should not have to use the --with-newlib switch, because obviously, we don't want to use newlib and we don't have it.

I'll be interested to know what you find out about this...

Eric Weddington