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.43) id 1EEBOO-0007LI-Am for garchives@archives.gentoo.org; Sat, 10 Sep 2005 19:52:04 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j8AJjpeh006637; Sat, 10 Sep 2005 19:45:51 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j8AJcX1s029747 for ; Sat, 10 Sep 2005 19:38:34 GMT Received: by zproxy.gmail.com with SMTP id x7so76680nzc for ; Sat, 10 Sep 2005 12:42:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bHWQ0wx9ajlfsvBKvdIFyIvvyFsMbKhMl7Nv39Nzgo3z5OuepF9gLLG5GfnLdU/W69ZY8s1/vIMYM6p5MIJrsGp8OumqzxYQf44WG2K8cqWfXUyUBHfeNN7oBSGGAR/f10jaXRo31yDU8V5QIavuffeVgVOn8zUyDwzHP2V7f7U= Received: by 10.36.222.18 with SMTP id u18mr1503065nzg; Sat, 10 Sep 2005 12:42:38 -0700 (PDT) Received: by 10.36.5.12 with HTTP; Sat, 10 Sep 2005 12:42:38 -0700 (PDT) Message-ID: <432beae0509101242d02a43d@mail.gmail.com> Date: Sat, 10 Sep 2005 12:42:38 -0700 From: Justin Patrin To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Nasty bugs in portage? In-Reply-To: <1126375769.5733.59.camel@localhost.localdomain> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <1126375769.5733.59.camel@localhost.localdomain> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j8AJcX1s029747 X-Archives-Salt: c0ae9c07-9be3-4181-b2f6-4d1e05a2bc08 X-Archives-Hash: 8a5bd64519359a1ba42edfc7703a67c6 On 9/10/05, Frank Schafer wrote: > ... or which distribution to install during less than 4 days? > > Hi list, > > as I wrote yesterday I planned to complete installation after work > (started ``emerge --emptytree system'' in the morning). > > When I returned home from work I found in the logs, that ``emerge > --emptytree system'' failed at package 28 of 186 > > python-fcksum-1.7.1 > i386-pc-linux-gnu-gcc ....bla...bla > ^ > | > +- !!!!!!!!!!!!!!!!!!!!! > > gcc-config error: > could not run/locate "i386-pc-linux-gnu-gcc" > > My architecture is i686 and it seems that 27 packages before > python-fchksum found the i686(that's SIX-eight-six)-pc-linux-gnu-gcc. > > Could be my fault. I had set up ACCEPT_KEYWORDS to "~x86". That's the first problem. Unless you want to deal with explosions, don't set your entire system to be unstable. That's a recipe for problems. Leave the global setting at stable. Then, if you need an unstable version use /etc/portage/package.keywords to set ~x86 for just the package you want to install. > > Today in the morning I started up from scratch. That's about an hour of > editing files, making file systems and so on, 1,5 hours of bootstrap.sh. > > ``emerge -p --emptytree system'' showed me, that it will install > python-fchksum with the ACCEPT_KEYWORDS="x86" too. So far, so good. > Yesterday I got a portage snapshot 20050907, today I got a portage > snapshot 20050908. Maybe the bug is fixed. So I started emerge system. > At least it didn't install two versions of gcc. That saved some time. It > ran 2,5 hours and ... > > ... kabooooom ... > > Unfortunately I can't tell you if the python-fchksum failure has gone > away. I didn't reach this ebuild :( > I suggest starting from a stage3 build. I've installed many stage 3 builds and it nearly always works with no breakage. Once your minimal system up and running (always go for minimal on the initial emerge, then boot into your system, then emerge more) then you can easily do an emptytree emerge to re-build things....if you *really* want to. I'm of the mind that starting with stage3 is perfectly fine. Eventually all of those packages will be updated and recompiled, so there's really no reason to do it manually right at the beginning. One more thing. What optimization setting(s) are you using? -- Justin Patrin -- gentoo-user@gentoo.org mailing list