avr-gcc-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-gcc-list] binutils 2.20


From: Weddington, Eric
Subject: RE: [avr-gcc-list] binutils 2.20
Date: Mon, 23 Nov 2009 15:00:47 -0700

 

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Rolf Ebert
> Sent: Monday, November 23, 2009 1:46 PM
> To: 'AVR-GCC'
> Subject: [avr-gcc-list] binutils 2.20
> 
> while building the compiler (gcc-4.3.3) I get the following error:
> 
> checking for avr-nm... 
> k/Data/Development/gcc-cvs/build/gcc-obj/./gcc/nm
> checking for avr-ranlib... /mingw/avr_43_gnat/avr/bin/ranlib
> checking for avr-strip... /mingw/avr_43_gnat/avr/bin/strip
> checking whether ln -s works... yes
> checking for avr-gcc... 
> /k/Data/Development/gcc-cvs/build/gcc-obj/./gcc/xgcc 
> -B/k/Data/Development/gcc-cvs/build/gcc-obj/./gcc/ 
> -B/mingw/avr_43_gnat/avr/bin/ -B/mingw/avr_43_gnat/avr/lib/ -isystem 
> /mingw/avr_43_gnat/avr/include -isystem 
> /mingw/avr_43_gnat/avr/sys-include  -mmcu=avrxmega4
> checking for suffix of object files... configure: error: 
> cannot compute 
> suffix of object files: cannot compile
> See `config.log' for more details.
> make[1]: *** [configure-target-libgcc] Error 1
> make[1]: Leaving directory `/k/Data/Development/gcc-cvs/build/gcc-obj'
> make: *** [all] Error 2
> 
> 
> I am using binutils 2.20 unpatched and the gcc-4.3.2 patches as 
> available from the WinAVR CVS repository.  The gcc patches apply all 
> cleanly against gcc-4.3.3.
> 
> It seams to me that the binutils still don't know about the 
> xmega chips.

That is correct. You have to use a patched binutils with a patched gcc. The 
xmega patches have been written by myself and Anatoly Sokolov and I haven't 
submitted them upstream yet.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]