[Top][All Lists]

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

RE: [avr-gcc-list] Latest working versions (ATmega324p)?

From: Weddington, Eric
Subject: RE: [avr-gcc-list] Latest working versions (ATmega324p)?
Date: Fri, 25 Apr 2008 08:39:46 -0600


> -----Original Message-----
> From: Bernard Fouché [mailto:address@hidden 
> Sent: Friday, April 25, 2008 2:48 AM
> To: Weddington, Eric
> Cc: Rick Mann; avr-gcc List
> Subject: Re: [avr-gcc-list] Latest working versions (ATmega324p)?
> Weddington, Eric wrote:
> > I'm currently working on a new WinAVR, with the offending 
> patch removed, and I hope that this will finally clear up the 
> problems. After I release WinAVR, and no one is screaming 
> that it is causing bad code to be generated then I will post 
> the patches on the WinAVR CVS.
> >
> > Sorry for all the hassle.
> >
> >
> >   
> Don't feel sorry, without people like you, Joerg, Dmitry, 
> Anatolv, Andy 
> and all the others involved in the avr-gcc toolchain and 
> related tools 
> like avrdude, we would be in a difficult situation ;)
> I think that the main problem is not about a particular release of a 
> particular package/software, but providing a central 
> information point 
> where someone would find all relevant information about the 
> toolchain. 
> In 6 month the problem with WinAvr20080411 may happen again 
> with a newer 
> release, and we'll be back to the beginning of this discussion.
> In the meantime people may have changed of tools because, 
> IMHO, at first 
> glance, being sure of having the latest avr-gcc toolchain is 
> a difficult 
> quest:

I understand your frustration because I experienced the same years ago. My 
apologies for letting it get to this point.

So here's the plan to help solve this situation:

- After the issues surrounding the April release of WinAVR are resolved, I want 
to ensure that more testing is put in place on a regular basis. This means 
build tests of source repository, and running various regression test suites. 
This may not catch unforseen errors, but it will certainly help that we don't 
regress. The point is to not get into the same situation that we are now with 
the April release of WinAVR. I have a mandate to put this system in place.

- I am planning to build and release Linux versions of the AVR toolchain on a 
regular basis, having it match WinAVR patch for patch. The work on this will be 
done in parallel with the testing above. I also have a mandate to do this.

- I would like to use some sort of publishing system for the WinAVR home page / 
web site. I have not updated the site in a long time because it is cumbersome. 
I have looked into some systems that don't work well for me. I prefer to use 
open source systems, so if someone has a suggestion of a tool that I can use 
that would be great. The emphasis has to be on *simplicity*. I don't want to 
have download and install a full LAMP system in order to do this. I just want 
it to be easy to update the pages rather than hand-coding the html.

I agree that the situation right now is confusing and unworkable. I personally 
don't like it this way. I want the situation to change, and importantly not to 
repeat itself.

Suggestions welcome.

Eric Weddington

reply via email to

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