Hi,
I was just wondering. Anyone have a preference for certain combinations of binutils, gcc, avrlibc that is different from the most current packages? If so, why?
Hi,
I was just wondering. Anyone have a preference for certain combinations of binutils, gcc, avrlibc that is different from the most current packages? If so, why?
Well, don't use GCC 4.0.1, it's got some serious bugs and optimization
regressions for the AVR target. If you'd like to test a GCC 4.x
version, use the latest snapshot.
binutils-2.16 is fine, the stable GCC version is 3.4.4.
avr-libc 1.4.0 is about to be released within probably one week (most
likely together with 1.2.6 that will be a bugfix-only upgrade to
1.2.5).
any preference for simply using the core gcc?
Sorry, what do you mean by that?
If you're referring to just their "core" distfile, yes, sure.
There's no need to download everything, kitchensink
included. I usually only use the "core" and "c++"
distfiles, as C++ is a possible option for the AVR. But
if you don't need C++, you don't even need to download
that.
I started AVR programming on CodeVisionAVR and am now using gcc, so I'm a little confused as to when C++ would be used to program the AVR.
BTW, Jörg, your tutorial on the avr libc website is fantastic - thanks. I know it took a lot of your time to do that for gcc newbies.