Hi, whoever of the two that are most "out of date" varies from time to time and from feature to feature. I guess it depends on where in their release cycle they are and how hard a time Atmel is having to get their patches accepted upstream. Also, there seems to be some patches in binutils that avr-develoopers depend on, that will never be accepted upstream (for whatever reason). Also, when using the Atmel release we get a full toolchain (gcc, binutils and libc) well tested to work for avr develoopment.
However, there is a version 3.4.5 release of the Atmel sources which we should upgrade to. It's still based on gcc 4.8.1 though. On Mon, Mar 9, 2015 at 7:51 PM, Gregor Riepl <onit...@gmail.com> wrote: > It seems avr-libc 1.8.1 will not build with gcc 4.8.1, but vanilla gcc 4.9.1 > works fine. I rolled my own .debs from the regular Debian gcc-4.9.1 sources > and vanilla 1.8.1 from the project website. > > As I understand, the AVR toolchain on Debian is built from Atmel sources, but > these are currently out of date. It seems Atmel toolchain developers are now > actively submitting patches to the gcc project, before making a new version of > their own toolchain available. This begs the question, wouldn't it be better > if Debian avr- packages started using vanilla sources instead? It would help > developers stay more up to date, and avoid relying on patched third party > sources. -- Håkan Ardö -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
