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

[Per Arnold Blaasmo]

Hi,
I tried to send this message to the mailing list, but it only got to the
persons on the CC.

Therefor I send it again to the list.

Per A.

-----Original Message-----
From: Per Arnold Blaasmo [mailto:address@hidden Sent: Thursday, March
24, 2011 5:14 PM
To: address@hidden
Cc: Boyapati, Anitha; Ruud Vlaming
Subject: Re: [avr-libc-dev] Patches for 1.7.1?

On -10. jan. -28163 20:59,  wrote:
> 
> 
>> -----Original Message-----
>> From: address@hidden
>> [mailto:address@hidden On
>> Behalf Of Boyapati, Anitha
>> Sent: Monday, March 21, 2011 10:56 PM
>> To: Ruud Vlaming; address@hidden
>> Subject: RE: [avr-libc-dev] Patches for 1.7.1?
>>
>> The build errors can be safely ignored.
> 
> That's an oxymoron. One cannot safely ignore build errors; they are
errors that completely stop the build! They can't be ignored!
> 
> What has to be done is to completely get rid of those patches in the
patch set.
> 
> 
Hi,
You guys must remember that these patches is the one Atmel currently
uses in the toolchain built for AVR Studio 5.

It is not the official avr-libc patches.
The avr-libc might or might not accept these patches in the future and
make a new version of avr-libc with these patches. Atmel hope the
project will want to use them.

Atmel will always be in front of the community project internally so
Atmel will probably always have patches to the latest public version.

Regarding build errors, they should of course not be there. But
currently the state of the AVR Studio 5 is changing before a public
release and there might be error.

Putting those patches on the website is an answer to the debate about
whether waiting until we do a official public release of AVR Studio 5 or
doing it with each beta release.

Regarding public or non-public devices. Atmel do have some devices that
needs some basic support and Atmel wants to have that in the toolchain.

For the non-public parts Atmel need to keep header files and some other
description files away from public. I am sure you all can understand
that.

avr-libc has made itself dependent on some header file info to be able
to generate a crt0.o file for each device. I would like that dependency
to be removed (like other libc project is not dependent on each devices
header files), so that Atmel can release non-public packages to
customers that are entitled to that to get support for an non-public
device without recompiling avr-libc. I hope that can be possible in the
future.

So "enjoy" the patches and Atmel will continue to try to support the
open source community as well as possible.

Regards
Per A.