The following packages are quite behind the times: * dev-embedded/avr-binutils Latest version available: 2.14 Latest version installed: 2.14 Size of downloaded files: 10,665 kB Homepage: http://sources.redhat.com/binutils Description: The GNU binutils for the AVR microcontroller architecture License: GPL-2 * dev-embedded/avr-gcc Latest version available: 3.3-r1 Latest version installed: 3.3-r1 Size of downloaded files: 22,898 kB Homepage: http://sources.redhat.com/binutils Description: The GNU C compiler for the AVR microcontroller architecture License: GPL-2 * dev-embedded/avr-libc Latest version available: 1.0.2-r1 Latest version installed: 1.0.2-r1 Size of downloaded files: 353 kB Homepage: http:////www.nongnu.org/avr-libc/ Description: Libc for the AVR microcontroller architecture License: GPL-2 I had no luck figuring out the package maintainer, but there are a number of new AVR devices that are not covered by the version in portage. THanks very much! Reproducible: Always Steps to Reproduce: 1. 2. 3. Sorry if this is not the correct way to report this, but I could not find another option. Thanks very much for you efforts! LOVE Gentoo :-).
I was hoping Joshua would commit the bug 52790 changes and this would remove all bar libc (see bug 52979). This is the way to report these kind of issues. If you could attempt updates these ebuilds it will be apprecated.
avr-libc 1.2.1 was just released late last week. I will submit an ebuild for it Monday some time. The others are available with a crossdev patch. Scott =)
Victoria (reporter) did email me some ebuilds) I haven't got around to looking at them yet. Victoria can you please attach them here so Scott can use/test them.
Created attachment 50023 [details] Updated ebuilds for avr tool chain. Work, but the tool chain still has problems with the new devices, perhaps only avr-libc, developing and further reports to follow.
Hello All, The dbuilds have been attached. The only thing I couldn't figure out was how to get the patches off the html/text pages, so I manually downloaded them and put them into the appropriate files directories. ALSO, there seems to be a problem with avr-libc (1.2.1) that is missing the linker(?) files for the new devices. What testing has been done indicates that they work for, at least, the devices I am using, if not for the new devices (the ATMega168 is the only one I have). The source compiles, but will not build. Waiting to hear more about this and will update as I know more. Once again, I am NO ebuild guru, but these do seem to work for what they do do. Thanks & Take care, V.
I have downloaded them and will try them tomorrow. One issue I have with the avr-libc ebuild is that at some point we are going to have to either make it support crossdev or make crossdev build it. Either way I think it will take modification of the ebuild. Mabye I will hack into crossdev again and see if I can get it to build avr-libc. It will take some work and be a major patch, but it does seem doable. I just wish we could get a patch to crossdev committed. Scott =)
All of the ebuilds compiled fine and seemed to work. I will do more testing this week. The only change I made was adding the ~amd64 keyword. I will have to work up a way to do more testing on gcc 3.4.3. I am still using 3.3 because the 3.4 series makes my binaries about 10% larger than 3.3. Binaries created with 3.4.x don't fit in my Tiny26 targets. ;) Scott =)
Scott any progress on testing?
I am out of town and have the flu. I am not going to get much done in the next week or so. I have installed avr-libc version 1.2.1 on 3 computers now and so far no problems with it. Avr-binutils I have on 2 computers and it works fine on both. Those installs include 1 amd64 and at least 1 i686. As far as avr-gcc I have installed it once, but had to remove it to do any real work because of the larger binaries it creates. Scott =)
Removing myself from this, hopfully. Outside of the bigger binaries, none of the programming software supports the new chips at this time. Maybe later the above issues will be fixed. In order to quit being reminded about it, I am marking it fixed. Couldn't find another possibility for this :-).
