From: Moritz Schlarb <mail@moritz-schlarb.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Failed to emerge dev-lang/python-2.5.4-r4
Date: Wed, 14 Sep 2011 02:17:54 +0200 [thread overview]
Message-ID: <4E6FF2B2.5090406@moritz-schlarb.de> (raw)
Hi at all!
For using Google App Engine, I wanted to emerge Python 2.5, so I did
emerge -av =dev-lang/python-2.5.4-r4
and everything went fine, until:
/usr/bin/install -c -m 644 pyconfig.h
/var/tmp/portage/dev-lang/python-2.5.4-r4/image//usr/include/python2.5/pyconfig.h
emake failed
* ERROR: dev-lang/python-2.5.4-r4 failed (install phase):
* emake altinstall maninstall failed
*
* Call stack:
* ebuild.sh, line 56: Called src_install
* environment, line 5753: Called die
* The specific snippet of code:
* emake DESTDIR="${D}" altinstall maninstall || die "emake
altinstall maninstall failed";
Doesn't make much sense to me, failing at installing to
python2.5-specific directories... I would investigate further, but I
don't know how to make portage tell me more about the error that occured!
But I'm eager to learn, would be great if someone could tell me where to
look for debugging infos.
I've uploaded:
complete build log: https://www.dropbox.com/s/t47wn56vtynlh3y/build.log
ebuild environment file:
https://www.dropbox.com/s/p1zdtxzewuc0745/environment
emerge --info =dev-lang/python-2.5.4-r4:
https://www.dropbox.com/s/8ran13tlk32p8f0/info
emerge -pqv =dev-lang/python-2.5.4-r4:
https://www.dropbox.com/s/rscag1azv3j5dwn/pqv
Looking forward to some instructions...
Regards,
Moritz
next reply other threads:[~2011-09-14 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 0:17 Moritz Schlarb [this message]
2011-09-14 0:52 ` [gentoo-user] Failed to emerge dev-lang/python-2.5.4-r4 Alex Schuster
2011-09-14 9:41 ` [gentoo-user] " Moritz Schlarb
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=4E6FF2B2.5090406@moritz-schlarb.de \
--to=mail@moritz-schlarb.de \
--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