RE: [avr-libc-dev] Patches for 1.7.1?

[Boyapati, Anitha]

>-----Original Message-----
>From: address@hidden
>[mailto:address@hidden On
>Behalf Of Joerg Wunsch
>Sent: Tuesday, March 22, 2011 11:21 AM
>To: address@hidden
>Subject: Re: [avr-libc-dev] Patches for 1.7.1?
>
>As Boyapati, Anitha wrote:
>
>> The build errors can be safely ignored. This is because of empty io
>> header files used for xmega32X1 and Xmega128B1. gcrt1.S requires
>> some definitions like __VECTORS_SIZE to be initialized in header
>> files. Since it does not find them, gcrt1.S could not expand
>> 'vectors' macro for those devices.
>
>But what's the point of adding support for devices that is not
>complete, and causes build errors?
>
>Given that we specifically released avr-libc 1.7.1 in preparation of
>the AVR Studio 5 release, I'm a little surprised the AVR Studio 5
>toolchain needs to apply private patches to avr-libc in their
>distribution at all.  IMHO, everything that is ready for the users
>could have been in the tree before, and everything that isn't, why
>is it released anyway?

True. The build problems did exist even before avr-libc-1.7.1 was integrated 
which went unnoticed because of tiny10 build problems. Once 1.7.1 was 
integrated, we realized the build issues with private parts and it was too late 
to change anything. 

As to why the patches are released, it is a little tricky part. The support 
exists is binutils and gcc. It is only the header files that cannot be made 
public. We have limited time to fix the issue and we were under the impression 
that every patch should be released.

This issue is taken up under high priority and is fixed internally. So the next 
release should have a proper fix.

Anitha