Hello, this is cvs ebuild for avr-libc. The avr-libc project is developing very fast but the most recent package in the tree (1.2.5) is quite old. Because there have been some important changes since that release, I'm coming out with cvs ebuild for the library. I dont think this ebuild will ever get to the tree, it's here just for people to download! Here is, IMO elegant, way how to install and use the ebuild without breaking your current environment: 1) copy the ebuild into /usr/portage/dev-embedded/avr-libc (or /usr/local/portage/cross-avr/avr-libc overlay) 2) rename the ebuild to avr-libc-1.3.ebuild (or avr-libc-1.5 , 1.2.6... whatever newer then 1.2.5-r1 is possible) 3) compute new digests "ebuild /....../avr-libc-1.3.ebuild digest" 4) update the avr-libc "emerge -vat =cross-avr/avr-libc-1.3" [Note]: I presume you had already installed previous version of avr-libc (together with gcc and binutils) by crossdev tool. [Know issue]: The ebuild uses "doc" keyword to build documentation. If you enable this flag and get some segfault error during making doc target. Try to disable it or downgrade media-libs/netpbm to 10.28 as its 10.29 version caused segfaults for me (amd64). Ebuild keywords are: ~x86 ~amd64 I succesfully tested on amd64 platform (today and many times before) Now if you suceed installing it, you can update everytime in the future by just simply re-emerging the cvs version of ebuild :) Enjoy! I hope this is usefull, if you encounter any problems just leave a comment in this bug report, thanks! [Warning]: It's possible (highly probable if you are using stdio.h api for exapmle) that your avr projects using avr-libc will stop working if you upgrade to current cvs version. It's because of major changes in api. Refer to Changelog and mail list archive at http://savannah.nongnu.org/projects/avr-libc/ . You have been warned! Yours, Ludek STEPAN
Created attachment 72739 [details] avr-libc-1.3.ebuild
Comment on attachment 72739 [details] avr-libc-1.3.ebuild Please use text-plain for text attachments.
(In reply to comment #2) > (From update of attachment 72739 [details] [edit]) > Please use text-plain for text attachments. > Im sorry, I thought 'auto' option would stand for it...
I'm sorry - I will not accept a live CVS ebuild for something as crucial as a libc. Especially not at this point, where the API is not stable... I appreciate your work on this, but it can not be accepted into portage.
(In reply to comment #4) Yeah, I can understand you very well and it's okay. There are many bug reports providing ebuilds that will never get into the tree, but I believe they are still usefull for some people. This ebuild has been laying quite long in my computer and I've been making big advantage of it... so now I provide it to the public. Or do you think I should post it somewhere else? Like gentoo-wiki or what?
Perhaps http://www.breakmygentoo.net/ will accept it?