Summary: | <mail-client/evolution-3.6 with USE=python fails to configure with python-3.2 as system interpreter | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jens Kasten <jens> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 10.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info
evolution build.log |
Description
Jens Kasten
2012-11-25 13:59:26 UTC
please add your emerge --info and the build.log as suggested by bugzilla/portage. Created attachment 330582 [details]
emerge-info
Created attachment 330584 [details]
evolution build.log
Did you run an emerge --sync before starting to build anything ? From the look of the ebuild it should automatically select python2 for build and it appears to work here. I did it now. But the same result. emerge --sync running always on the local fileserver from where I get the portage tree. (In reply to comment #0) > > checking for python... /usr/bin/python > checking for python compile flags... File "<string>", line 1 > import sys ; print sys.prefix > ^ > SyntaxError: invalid syntax > File "<string>", line 1 > import sys ; print sys.exec_prefix > ^ > SyntaxError: invalid syntax > File "<string>", line 1 > import sys ; print sys.version[0:3] > ^ > SyntaxError: invalid syntax > File "<string>", line 1 > import sys ; print sys.version[0:2] > ^ > SyntaxError: invalid syntax > configure: error: Can't find Python.h > Same thing happens for me. Sync'ed yesterday afternoon the last time. Fixed in cvs, thanks for reporting. Evolution-3.4 and earlier used a non-standard way of detecting the python interpreter, so to force it to use the correct python, we need to add pythonpath="$(PYTHON -2 -a)" to configure arguments.
> 26 Nov 2012; Alexandre Rostovtsev <tetromino@gentoo.org>
> evolution-2.32.3-r1.ebuild, evolution-3.2.3-r1.ebuild,
> evolution-3.4.4.ebuild:
> Fix build failure with python3 as system interpreter (bug #444694, thanks to
> Jens Kasten).
|