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

[Boyapati, Anitha]

>-----Original Message-----
>From: Weddington, Eric
>Sent: Monday, March 21, 2011 8:37 PM
>To: Boyapati, Anitha; Ruud Vlaming; address@hidden
>Subject: RE: [avr-libc-dev] Patches for 1.7.1?
>
>
>
>> -----Original Message-----
>> From: address@hidden
>> [mailto:address@hidden On
>> Behalf Of Boyapati, Anitha
>> Sent: Monday, March 21, 2011 9:00 AM
>> To: Ruud Vlaming; address@hidden
>> Subject: RE: [avr-libc-dev] Patches for 1.7.1?
>>
>>
>> >
>> >Furthermore, the first two patches (40, 41) can be applied,
>> >but compilation results in an error:
>> > ... avr-libc-1.7.1/crt1/gcrt1.S:179: Error: non-constant expression in
>> >".if" statement
>> >The last application cannot be applied at all:
>> >  patching file ./include/avr/power.h
>> >  Hunk #1 FAILED at 74.
>> >  Hunk #2 FAILED at 146.
>> >  Hunk #3 FAILED at 170.
>> >  Hunk #4 FAILED at 254.
>> >  Hunk #5 FAILED at 338.
>> >
>> >I am curious at your opinion.
>> >
>>
>>
>> I think those patches are meant for some test devices. They contain dummy
>> header files. Hence build errors. They can be ignored.
>
>
>Are they for test devices? Or are they for new devices?

New devices yet internal and non-public.

>
>And, really, if they cause build errors and can be ignored, then they
>should not be in the bundled source code on the Atmel Norway website to
>begin with. 

The policy is to releases sources that has been used to build the toolchain.

> This causes a disservice to the user community.

This is not intentional. And moreover they will not be prolonged. The errors 
are similar to AVR tiny10 errors caused by avrtiny10. These were realized in 
much later stages when avr-libc 1.7.1 was used.

Anitha