From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OELkk-0003jB-Im for garchives@archives.gentoo.org; Tue, 18 May 2010 12:18:38 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 99A71E0766; Tue, 18 May 2010 12:18:02 +0000 (UTC) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 557BCE0766 for ; Tue, 18 May 2010 12:18:02 +0000 (UTC) Received: by wyb36 with SMTP id 36so2296118wyb.40 for ; Tue, 18 May 2010 05:18:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=IzSHHkFQ/rpQCms7YirVL63i1Hui5nkWS4baoCc4uU4=; b=GwE1TjDQuP9u6ccRWSr8hcX3so7UJftPU7scpUhHK17xhzcFLamj7GY3kMBnBqYsGP fkqvoVve3LwMDyyLECB+hPx6Pxup4KsvzEwMSu6OdpufqGYVw8BocCIh1sRfNGX79xfB QnzAbRvCNpIUR3xhd8H7PZzeMAQeq5WgT+oPo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=u4Tn6+JLd4j8NRgR3JGNJ4Q01t0OQuRwo3PVXMj06RKmKURPc+i1nwIQxTQ7SI0Fn8 foQhQXPFrTly2bF8tzuS1GVTkusIc+FeQSIoE1neNMeXqWFN5ffliK/iOYB/vTH3T0lT XrWO6OyxwSXzvmaXy2/1Th8kXVKt5vzTOMuuA= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.89.11 with SMTP id b11mr4147206wef.32.1274185081690; Tue, 18 May 2010 05:18:01 -0700 (PDT) Received: by 10.216.178.206 with HTTP; Tue, 18 May 2010 05:18:01 -0700 (PDT) In-Reply-To: <4BF283FB.4040902@gmail.com> References: <4BEFEEB8.9060301@gmail.com> <201005161544.05855.alan.mckinnon@gmail.com> <4BF283FB.4040902@gmail.com> Date: Tue, 18 May 2010 13:18:01 +0100 Message-ID: Subject: Re: [gentoo-user] emerge portage error From: Mick To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 03834b8e-4d3d-4399-9e96-afd2ffee631a X-Archives-Hash: 064d4311c1803272e695a1399357712c On 18 May 2010 13:11, Barry Jibb wrote: > On 16/05/10 14:44, Alan McKinnon wrote: >> >> On Sunday 16 May 2010 15:10:16 Simon wrote: >> >>> >>> Hi, >>> >>> Please help me to get rid of this error while emerging portage: >>> # emerge portage >>> >> >> [snip] >> >> Yea gods, the youth of today. In my day, when I was a little >> whipper-snapper, >> we actually read the ebuild. Why because? Because there was no-one else >> around >> to do our looking by proxy for us! >> >> So, in the interest of decomming the proxy in my head, herewith the magi= c >> incantations to make your problem go "Poof!" and disappear: >> >> Firstly, you have tools to help. equery, euse, and many more. Learn how = to >> use >> them, and use them. >> >> Secondly, read the ebuild. portage does what the ebuild says so the mast= er >> reference to figure out why portage wants to do something is in the ebui= ld >> (or >> eclasses that it inherits). >> >> >>> >>> =A0 * "bsddb" module is out-of-date and no longer maintained inside >>> dev-lang/python. It has >>> =A0 * been additionally removed in Python 3. You should use external, >>> still maintained "bsddb3" >>> =A0 * module provided by dev-python/bsddb3 which supports both Python 2 >>> and Python 3. >>> =A0 * >>> =A0 * ERROR: dev-lang/python-2.5.4-r4 failed. >>> =A0 * Call stack: >>> =A0 * =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ebuild.sh, line =A0 49: =A0Called = pkg_setup >>> =A0 * =A0 python-2.5.4-r4.ebuild, line =A0 64: =A0Called built_with_use >>> 'pkg_setup' 'pkg_setup' >>> =A0 * =A0 =A0 =A0 =A0 =A0 =A0eutils.eclass, line 1862: =A0Called die >>> =A0 * The specific snippet of code: >>> =A0 * =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0die) =A0 die "$PKG does not >>> actually support the $1 USE flag!";; >>> =A0 * =A0The die message: >>> =A0 * =A0 sys-devel/gcc-4.1.2 does not actually support the libffi USE = flag! >>> >> >> =A0From the ebuild: >> pkg_setup() { >> =A0 =A0 =A0 =A0 if use berkdb; then >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ewarn "\"bsddb\" module is out-of-date a= nd no longer >> maintained inside dev-lang/python. It has" >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ewarn "been additionally removed in Pyth= on 3. You should >> use >> external, still maintained \"bsddb3\"" >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ewarn "module provided by dev-python/bsd= db3 which supports >> both Python 2 and Python 3." >> =A0 =A0 =A0 =A0 fi >> >> =A0 =A0 =A0 =A0 if built_with_use sys-devel/gcc libffi; then >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 die "Reinstall sys-devel/gcc with \"libf= fi\" USE flag >> disabled" >> =A0 =A0 =A0 =A0 fi >> } >> >> >> So, to get rid of the bsddb ewarn, you need to remove that "berkdb" from >> USE. >> >> And the build failure is staring you right there in the face. As we say >> here >> at the tip of Africa, "As dit 'n slang was, het dit jou gepik" [If it we= re >> a >> snake, it would have already bitten you]. >> >> >> You have "USE=3Dlibffi" which doesn't work. Remove it, sync the tree, >> rebuild >> world. (your portage and gcc versions have updates available, even on >> stable) >> >> >> >> > > How do i unsubscribe from the list? I love it, but i subscribed in error = and > I cant seem to stop it! If you will be hijacking threads like this then you better unsubscribe soon please! Read the headers of this email message for instructions. --=20 Regards, Mick