From: Simon <owtneg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] emerge portage error
Date: Sun, 16 May 2010 16:10:16 +0300 [thread overview]
Message-ID: <4BEFEEB8.9060301@gmail.com> (raw)
Hi,
Please help me to get rid of this error while emerging portage:
# emerge portage
Calculating dependencies... done!
>>> Verifying ebuild Manifests...
>>> starting parallel fetching pid 6030
>>> Emerging (1 of 2) dev-lang/python-2.5.4-r4 to /
* Python-2.5.4.tar.bz2 RMD160 SHA1 SHA256 size ;-)
...
[ ok ]
* python-gentoo-patches-2.5.4-r3.tar.bz2 RMD160 SHA1 SHA256 size ;-)
...
[ ok ]
* checking ebuild checksums ;-)
...
[ ok ]
* checking auxfile checksums ;-)
...
[ ok ]
* checking miscfile checksums ;-)
...
[ ok ]
* checking Python-2.5.4.tar.bz2 ;-)
...
[ ok ]
* checking python-gentoo-patches-2.5.4-r3.tar.bz2 ;-)
...
[ ok ]
* "bsddb" module is out-of-date and no longer maintained inside
dev-lang/python. It has
* been additionally removed in Python 3. You should use external,
still maintained "bsddb3"
* module provided by dev-python/bsddb3 which supports both Python 2
and Python 3.
*
* ERROR: dev-lang/python-2.5.4-r4 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* python-2.5.4-r4.ebuild, line 64: Called built_with_use
'pkg_setup' 'pkg_setup'
* eutils.eclass, line 1862: Called die
* The specific snippet of code:
* die) die "$PKG does not
actually support the $1 USE flag!";;
* The die message:
* sys-devel/gcc-4.1.2 does not actually support the libffi USE flag!
*
* 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/dev-lang/python-2.5.4-r4/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-lang/python-2.5.4-r4/temp/die.env'.
*
* Messages for package dev-lang/python-2.5.4-r4:
*
* ERROR: dev-lang/python-2.5.4-r4 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* python-2.5.4-r4.ebuild, line 64: Called built_with_use
'pkg_setup' 'pkg_setup'
* eutils.eclass, line 1862: Called die
* The specific snippet of code:
* die) die "$PKG does not
actually support the $1 USE flag!";;
* The die message:
* sys-devel/gcc-4.1.2 does not actually support the libffi USE flag!
*
* 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/dev-lang/python-2.5.4-r4/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-lang/python-2.5.4-r4/temp/die.env'.
*
* "bsddb" module is out-of-date and no longer maintained inside
dev-lang/python. It has
* been additionally removed in Python 3. You should use external,
still maintained "bsddb3"
* module provided by dev-python/bsddb3 which supports both Python 2
and Python 3.
next reply other threads:[~2010-05-16 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 13:10 Simon [this message]
2010-05-16 13:44 ` [gentoo-user] emerge portage error Alan McKinnon
2010-05-18 12:11 ` Barry Jibb
2010-05-18 12:18 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BEFEEB8.9060301@gmail.com \
--to=owtneg@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox