Re: [avr-libc-dev] avr-libc 1.6.8 [was: duplicating avr-libc from winavr]

[Galen Seitz]

Joerg Wunsch wrote:
> I just decided to roll a new release.  Originally, my intention was to
> fix some of the more critical bugs before doing that, but I realize I
> currently don't have the time to do it right.  As Eric recently
> released WinAVR without an avr-libc release (sorry for that), and as
> my FreeBSD port was also already breaking into pieces due to the
> doxygen issue (a doxygen-generated filename changed), I decided to
> just roll a release from the 1.6 branch "as-is".
>
> There are just two differences to Eric's WinAVR version.  One is the
> doxygen-related bugfix that doesn't affect end users at all, only
> those who are building the documentation using the latest doxygen
> version (i.e., typically those who roll a binary distribution).
>
> The other one is a bugfix that rewrote clock_prescale_set() as an
> inlined function rather than being a macro.  The macro version
> stumbled upon some USB code that (stupidly) added parentheses on the
> right-hand side of a macro around clock_prescale_set().
>
> So Galen, if you can live with these two differences to
> WinAVR-20100110, you might as well use 1.6.8 instead.

OK, I'm finally getting back to this.  I've downloaded and unpacked 
avr-libc-1.6.8.tar.bz2.  I have also checked out the WinAVR-20100110 
tag using the following command:
cvs -d:pserver:address@hidden:/sources/avr-libc export -r 
WinAVR-20100110 avr-libc

When comparing the two trees, I get some unexpected differences. 
Among them are the following files.

Only in avr-libc-WinAVR-20100110/doc/api: unjs.pl
Only in avr-libc-WinAVR-20100110/include/avr: iotn10.h
Only in avr-libc-WinAVR-20100110/include/avr: iotn4.h
Only in avr-libc-WinAVR-20100110/include/avr: iotn5.h
Only in avr-libc-WinAVR-20100110/include/avr: iotn9.h

Can you explain why these include files are not part of the tarball? 
I guess the bootstrap process removes them, since they are not present 
in an actual WinAVR-20100110 install, but I'd like to understand why.

thanks,
galen
--
Galen Seitz
address@hidden