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 1I531X-0007F3-Fk for garchives@archives.gentoo.org; Sun, 01 Jul 2007 17:15:47 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l61HFDO6004338; Sun, 1 Jul 2007 17:15:13 GMT Received: from sccrmhc15.comcast.net (sccrmhc15.comcast.net [63.240.77.85]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l61HFCY3004327 for ; Sun, 1 Jul 2007 17:15:12 GMT Received: from [192.168.1.4] (c-69-140-18-238.hsd1.md.comcast.net[69.140.18.238]) by comcast.net (sccrmhc15) with ESMTP id <2007070117151101500j0kc0e>; Sun, 1 Jul 2007 17:15:11 +0000 Message-ID: <4687E11E.9030501@gentoo.org> Date: Sun, 01 Jul 2007 13:15:10 -0400 From: Kumba User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) 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> In-Reply-To: <468761C6.2020607@uni-bonn.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: bd684bcb-93d7-44a2-9d1d-d0b747e479d6 X-Archives-Hash: f743da2245b62802d273a435a7a71912 Mathias W. wrote: > Hi, > As I mentioned previously without getting an answer > (http://archives.gentoo.org/gentoo-mips/msg_00589.xml) I'm still having > problems with compiling the kernel: > > LD .tmp_vmlinux1 > lib/lib.a: could not read symbols: Archive has no index; run ranlib to > add one > make: *** [.tmp_vmlinux1] Error 1 > > I've been always told to run binutils-config which I've done now a > thousand times. I tried to switch compilers several times. I even > emerged an old version of binutils (with USE="multislot") to switch to > (and back) - nothing helped. > Has anybody an idea what to try before I'm going to setup the system > again from scratch? 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. 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. I can only think that this is residual goop leftover, possibly form that ldscripts bug. Since catalyst stages nuke everything on a rebuild, when the ldscripts bug was fixed, I may've just skipped over this issue by the nuking. Cause else, this would be a kernel build failure, and I should've ran into it by now. As a last afterthought, make sure mips64-unknown-linux-gnu-ranlib exists and can be ran. --Kumba -- Gentoo/MIPS Team Lead "Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond -- gentoo-mips@gentoo.org mailing list