As Boyapati, Anitha wrote: > The build errors can be safely ignored. This is because of empty io > header files used for xmega32X1 and Xmega128B1. gcrt1.S requires > some definitions like __VECTORS_SIZE to be initialized in header > files. Since it does not find them, gcrt1.S could not expand > 'vectors' macro for those devices.
But what's the point of adding support for devices that is not complete, and causes build errors? Given that we specifically released avr-libc 1.7.1 in preparation of the AVR Studio 5 release, I'm a little surprised the AVR Studio 5 toolchain needs to apply private patches to avr-libc in their distribution at all. IMHO, everything that is ready for the users could have been in the tree before, and everything that isn't, why is it released anyway? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-libc-dev
