From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1I5Hkb-0007Xg-Pl for garchives@archives.gentoo.org; Mon, 02 Jul 2007 08:59:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l628wxma015212; Mon, 2 Jul 2007 08:58:59 GMT Received: from uni-bonn.de (mail.uni-bonn.de [131.220.15.112]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l628wxqK015207 for ; Mon, 2 Jul 2007 08:58:59 GMT Received: from [131.220.136.22] ([131.220.136.22] verified) by uni-bonn.de (CommuniGate Pro SMTP 5.0.8) with ESMTP id 49683537 for gentoo-mips@lists.gentoo.org; Mon, 02 Jul 2007 10:58:59 +0200 Message-ID: <4688BE52.3030505@uni-bonn.de> Date: Mon, 02 Jul 2007 10:58:58 +0200 From: "Mathias W." Organization: privat User-Agent: Thunderbird 2.0.0.4 (X11/20070625) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-mips@gentoo.org Reply-to: gentoo-mips@lists.gentoo.org MIME-Version: 1.0 To: gentoo-mips@lists.gentoo.org Subject: Re: [gentoo-mips] Still Problems with compiling the kernel References: <468761C6.2020607@uni-bonn.de> <4687E11E.9030501@gentoo.org> In-Reply-To: <4687E11E.9030501@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 6ab571ca-f47e-4af8-bca9-d9852bedab5d X-Archives-Hash: 3f81c0b1bc02b4801066c3f50bbe4811 Kumba schrieb: > I did hit the ldscripts error, which needed a fix in binutils-config. > But this ranlib-based one, I haven't hit in the last few times I've run > catalyst to build newer livecds. All I can say, is use crossdev to > completely remove all traces of cross-compilers, then follow behind it > in /usr and remove any left overs that might be remaining (usually in > /usr/${CHOST}/*). Then, remove all your kernel trees. I did this and hopefully removed everything which looked like mips64. > Remerge everything, using gcc-4.1.2 and binutils-2.17, and cross > fingers. Make sure you're running "make vmlinux" for 64bit targets > (IP28, IP27, IP30) or vmlinux.32 for quasi-64bit targets (IP22, IP32). > Also make sure you have the latest crossdev too. Now I emerged gcc-4.1.2 but then kgcc64-4.1.2 fails during compile: rm -f include/limits.h cp xlimits.h include/limits.h cp /var/tmp/portage/sys-devel/kgcc64-4.1.2/work/gcc-4.1.2/gcc/unwind-generic.h include/unwind.h chmod a+r include/limits.h rm -f include/README cp /var/tmp/portage/sys-devel/kgcc64-4.1.2/work/gcc-4.1.2/gcc/../fixincludes/README-fixinc include/README chmod a+r include/README echo timestamp > stmp-int-hdrs make[2]: *** No rule to make target `/usr/bin/mips64-unknown-linux-gnu-as', needed by `stamp-as'. Stop. make[2]: Leaving directory `/var/tmp/portage/sys-devel/kgcc64-4.1.2/work/build/gcc' make[1]: *** [all-gcc] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/kgcc64-4.1.2/work/build' make: *** [all] Error 2 !!! ERROR: sys-devel/kgcc64-4.1.2 failed. Call stack: ebuild.sh, line 1615: Called dyn_compile ebuild.sh, line 972: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile ebuild.sh, line 1305: Called toolchain_src_compile toolchain.eclass, line 26: Called gcc_src_compile toolchain.eclass, line 1541: Called gcc_do_make toolchain.eclass, line 1415: Called die !!! emake failed with all !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/sys-devel/kgcc64-4.1.2/temp/build.log'. ---------------------------------------- Now I'm not sure if this may be in relation to the cleaning because I had kgcc64-4.1.1 before. (I'm pretty sure that I did too much cleaning because kgcc64-4.1.1 shows the same error now) I think I rebuild this machine from Scratch: is there a newer stage3 available than this: stage3-mips4-2006.0.tar.bz2 ? -- Mathias Weigt -- gentoo-mips@gentoo.org mailing list