Hello When I try to update from cross-avr/avr-libc-1.2.3 to 1.2.5 on AMD64, I get the following error: ... Making all in crt1 make[3]: Entering directory `/var/tmp/portage/avr-libc-1.2.5/work/avr-libc-1.2.5/avr3/obj-avr/crt1' avr-gcc -I../../../include -I../../../common -mmcu=avr3 -x assembler-with-cpp -Wa,-gstabs -mmcu=atmega103 -c ../../../crt1/gcrt1.S -o crtm103.o cc1: error: invalid option '64' make[3]: *** [crtm103.o] Error 1 ... I think it's because of ABI stuff, so I offer this patch which works for me: --- /root/avr_fix/avr-libc-1.2.5.ebuild 2005-08-11 11:43:02.000000000 +0200 +++ avr-libc/avr-libc-1.2.5.ebuild 2005-08-11 12:09:06.000000000 +0200 @@ -26,6 +26,7 @@ src_compile() { export CC=avr-gcc + export CFLAGS_$ABI= strip-flags strip-unsupported-flags
re-emerge crossdev and try again ... i added fake ABI support to it but dont recall if i rev bumped it or not
Yes, you are right. I did the following 1. # emerge crossdev >>> did solve nothing 2. # emerge =cross-avr/avr-libc-1.2.5 >>> cc1: error: invalid option'64' 3. # crossdev --libc 1.2.5 -t avr >>> updated fine Does it mean that I can emerge avr-libc only through crossdev program? I can simply #emerge cross-dev/gcc without any problems, is there any way how to include ABI support into avr-libc ebuild like it is done in gcc ebuild and toolchain eclass so people can easily emerge cross-avr/avr-libc ?
personally i think the current state of the ABI var is screwed up, it just breaks crap like this we should add ABI to the avr-libc ebuild too though since it is possible to upgrade avr-libc once you've installed it with crossdev ...
yeah, that's exactly what i think... I'll try to look into it :)
force setting of ABI to a bogus value since i doubt we'll get the ABI crap fixed anytime soon
