All the sudden I noticed that I had no atmega168 support, seemed that portage had decided to downgrade my avr-gcc to 3.4.3. I tried to upgrade it, but it refused: rogue:fredde:/usr/portage>ACCEPT_KEYWORDS="~x86" emerge -pv cross-avr/gcc These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] cross-avr/gcc-3.4.3.20050110-r2 (-altivec) -bootstrap -boundschecking -build -fortr an -gcj -gtk -hardened -ip28 (-multilib) -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp -objc -s tatic -vanilla 0 kB [1] [ebuild N ] sys-libs/libstdc++-v3-3.3.6 -build (-multilib) +nls -nptl 23,410 kB Total size of downloads: 23,410 kB Portage overlays: [1] /usr/local/portage (It didn't matter which ACCEPT_KEYWORD I used, but I got errors on the stdlibc++ if I didn't use ~x86 and forgot about USE=nocxx) but: rogue:fredde:local/portage/cross-avr/gcc>sudo cp gcc-3.4.4-r1.ebuild gcc-3.4.4.ebuild rogue:fredde:local/portage/cross-avr/gcc>emerge -pv cross-avr/gcc These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] cross-avr/gcc-3.4.4 (-altivec) -bootstrap -boundschecking -build -fortran -gcj -gtk -hardened -ip28 (-multilib) -multislot (-n32) (-n64) +nls -nocxx -nopie -nossp -objc -static -vanil la 0 kB [1] Total size of downloads: 0 kB Portage overlays: [1] /usr/local/portage Is there any reason why it suddenly would accept the 3.4.4 ebuild if I just skipped the -r1? Looks like an error somewhere... Perhaps mine? :) Reproducible: Always Steps to Reproduce: 1. 2. 3.
http://www.gentoo.org/cgi-bin/viewcvs.cgi/dev-embedded/avr-gcc/ChangeLog?rev=1.10&view=log
Why make this INVALID and a link to ChangeLog for avr-gcc? This is not avr-gcc related. This is cross-avr/gcc related, which is EXACTLY what sys-devel/crossdev creates for you. I'm reopening and hope for a better explanation of how this is related to cross-dev/gcc and 3.4.4-r1 v/s 3.4.4.
dev-embedded/avr-gcc ebuild does not exist any more, so don't report bugs about it. Besides, I have no clue what ebuild is this bug about...
*sigh* Atleast I tried...
> This is not avr-gcc related. This is cross-avr/gcc related, which is EXACTLY what sys-devel/crossdev creates for you. Please write a better bug report next time. At best you start the summary with "$category/$ebuild-x.y: ". Don't expect that those who wrangle bug reports are familiar with all 10.000+ packages in the repository.
sorry, but this is something you're going to have to hand fix yourself on your system ... the issue is that when you run crossdev, it creates local keyword masks in /etc/portage files so that you can emerge the correct versions in your case, you installed cross-avr/gcc-3.4.4 which means you should have something like this in /etc/portage/package.keywords: =cross-avr/gcc-3.4.4 ~x86 since we punted the gcc-3.4.4 ebuild in favor of 3.4.4-r1, and your local masking still says '3.4.4', portage 'rightfully' is trying to downgrade it the fix is to edit your local /etc/portage/package.keywords file and change the version from '3.4.4' to '3.4.4-r1' btw, in the future, you can assign avr-related bugs to either toolchain@gentoo or embedded@gentoo for faster processing
Thanks. I suspected the error was on my side. I tried to figure out what caused the downgrade. Missed the package.keywords. Not much info on what crossdev really does... I'll try to write a better bugreport next time. Closing it for real.
