Hi *! cdk-4.9.11.20031210-r1 fails to emerge as some as some object files aren't found. This are the error messages: i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../crti.o: No such file or directory i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/crtbeginS.o: No such file or directory i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/crtendS.o: No such file or directory i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../crtn.o: No such file or directory make: *** [libcdk.la] Error 1 This is because there is no 3.3.5 directory in /usr/lib/gcc-lib/i686-pc-linux-gnu but something like 3.3.5-20050130 (at least on my system). I fixed this issue by adding a link with: ln -sf /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130 /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5 I don't know if this is fixable in the cdk ebuild or if it is a good idea to add this link with the glibc ebuild. This happens on x86 32bit and x86 64bit, but I guess on other platforms too. See http://forums.gentoo.org/viewtopic-t-333151-start-0-postdays-0-postorder-asc-highlight-.html?sid=ee6b4fa66494a2e327e5e25ea95ecbd0 cu Sebastian Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" emerge =cdk-4.9.11.20031210-r1 Actual Results: i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../crti.o: No such file or directory i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/crtbeginS.o: No such file or directory i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/crtendS.o: No such file or directory i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../crtn.o: No such file or directory make: *** [libcdk.la] Error 1 Expected Results: clean emerge
Run fix_libtool_files.sh 3.3.5 *** This bug has been marked as a duplicate of 84324 ***
Actually, fix_libtool_files.sh 3.3.5 does not fix the problem for me.
I had the same problem. fix_libtool_files.sh 3.3.5 didn't help me, too. My solution was to rebuild libtool.
*** Bug 105338 has been marked as a duplicate of this bug. ***
Follow http://www.gentoo.org/doc/en/gcc-upgrading.xml and upgrade gcc to 4.1.1