Re: [avr-gcc-list] avr-gcc/avr-binutils/avr-libc and the ATMega168 - what am I doing wrong, tnx!

[Rod Moffitt]

My build script has support for the GCC and binutils patches for the new 
mega48/88/168 devices. It will build insight, GCC, binutils and avr-libc. 
Of course it is targeted towards UNIX systems (although it should work for 
cygwin).

All you need to do is download the script and the tar-balls (all available 
from my site) and then run the script.

http://rod.info/avr.html

- Rod

--
                         ___  ____  ___    _      ___
 Rod Moffitt            / _ \/ __ \/ _ \  (_)__  / _/__
 http://rod.info       / , _/ /_/ / // / / / _ \/ _/ _ \
 address@hidden /_/|_|\____/____(*)_/_//_/_/ \___/
 =======================================================
 ~ Where loved ones are remembered http://memoriam.org ~

On Fri, 28 Jan 2005, E. Weddington wrote:

> Victoria Welch wrote:
>
> > Hello Ned and Eric,
> >
> > Thank you VERY much for the reply!
> <snip>
>
> > Fatal error: unknown MCU: atmega168
> > [ ... ]
> >
> >
> > As for the patches at:
> >
> > http://savannah.nongnu.org/patch/index.php?func=detailitem&item_id=2923#attached
> >
> > I have no idea if these are relevant at this point.
>
> I just told you that you did need them.
>
> Those patches are for:
> binutils 2.15
> gcc 3.4.x
> avr-libc < 1.20
> You'll find seperate patches in that Tracker (at the URL above) for each of 
> thos projects.
>
> If you are using avr-libc = 1.20 or 1.2.1, then you don't need to patch it.
> If you are using gcc = 3.4.x, then you need the gcc patch.
> If you are using gcc = current CVS HEAD (future 4.0.0), then you don't need 
> to patch it.
> If you are using binutils = 2.15, then you need the binutils patch.
> If you are using binutils = current CVS HEAD (future 2.16), then you don't 
> need to patch it.
>
> Currently the only *released* project that has support for that device is 
> avr-libc. Binutils and GCC do not have any *released* version that has 
> support this device.
>
> I would *strongly* suggest that you do not use GCC CVS HEAD for development 
> as it is still highly unstable. You can use it if you're just curious as to 
> how the GCC development is going. But I would recommend that you use GCC 
> 3.4.3.
>
> Eric
>
>
> _______________________________________________
> avr-gcc-list mailing list
> address@hidden
> http://www.avr1.org/mailman/listinfo/avr-gcc-list