376095 – dev-lang/python-3.2-r1: fails to build

Bug 376095 - dev-lang/python-3.2-r1: fails to build

Summary: dev-lang/python-3.2-r1: fails to build

Status:	RESOLVED DUPLICATE of bug 376083

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-07-23 13:07 UTC by Stefan Huber
Modified:	2011-07-23 13:14 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
The build.log for the failed emerge. (build.log,547.63 KB, text/x-log) 2011-07-23 13:09 UTC, Stefan Huber	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stefan Huber 2011-07-23 13:07:28 UTC

dev-lang/python-3.2-r1 fails to build with the following error:

cp: cannot stat `/var/tmp/portage/dev-lang/python-3.2-r1/image//usr/lib64/python3.2/plat-linux2': No such file or directory

This bug appears to be related to bug #374579. Note that I find the following plat-linux* files on my filesystem:
/var/tmp/portage/dev-lang/python-3.2-r1/work/Python-3.2/Lib/plat-linux3
/var/tmp/portage/dev-lang/python-3.2-r1/work/Python-3.2/Lib/plat-linux2
/var/tmp/portage/dev-lang/python-3.2-r1/image/usr/lib64/python3.2/plat-linux3

This is the reason why line 299-300 in the ebuild failed. Just FYI, after commenting these lines out, emerge worked as expected and /usr/lib64/python3.2/plat-linux3 exists.


Reproducible: Always

Comment 1 Stefan Huber 2011-07-23 13:09:14 UTC

Created attachment 280733 [details]
The build.log for the failed emerge.

Comment 2 Stefan Huber 2011-07-23 13:12:38 UTC

I may also mention that my current kernel is from gentoo-sources-3.0.

Comment 3 Alex Legler (RETIRED) archtester

2011-07-23 13:14:58 UTC

(In reply to comment #2)
> I may also mention that my current kernel is from gentoo-sources-3.0.

congratulations

*** This bug has been marked as a duplicate of bug 376083 ***