Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 518698 - USE="-python" emerge intel-gpu-tools fails
Summary: USE="-python" emerge intel-gpu-tools fails
Status: RESOLVED DUPLICATE of bug 518538
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-31 21:27 UTC by James Ausmus
Modified: 2014-07-31 23:14 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Ausmus 2014-07-31 21:27:01 UTC
# USE="-python" emerge -v intel-gpu-tools

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N     ] x11-apps/intel-gpu-tools-1.7  USE="-python" PYTHON_SINGLE_TARGET="-python3_3 -python3_4" PYTHON_TARGETS="python3_3 -python3_4" VIDEO_CARDS="nouveau" 0 kB

Total: 1 package (1 new), Size of downloads: 0 kB


>>> Verifying ebuild manifests

>>> Emerging (1 of 1) x11-apps/intel-gpu-tools-1.7::gentoo
 * intel-gpu-tools-1.7.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                                                             [ ok ]
 * No Python implementation selected for the build. Please set
 * the PYTHON_SINGLE_TARGET variable in your make.conf to one
 * of the following values:
 * 
 * python3_3 python3_4

 * ERROR: x11-apps/intel-gpu-tools-1.7::gentoo failed (setup phase):
 *   No supported Python implementation in PYTHON_SINGLE_TARGET.
 * 
 * Call stack:
 *                 ebuild.sh, line  93:  Called pkg_setup
 *                 ebuild.sh, line 317:  Called python-single-r1_pkg_setup
 *   python-single-r1.eclass, line 261:  Called python_setup
 *   python-single-r1.eclass, line 251:  Called die
 * The specific snippet of code:
 *              die "No supported Python implementation in PYTHON_SINGLE_TARGET."
 * 
 * If you need support, post the output of `emerge --info '=x11-apps/intel-gpu-tools-1.7::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=x11-apps/intel-gpu-tools-1.7::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/temp/die.env'.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/work/intel-gpu-tools-1.7'

>>> Failed to emerge x11-apps/intel-gpu-tools-1.7, Log file:

>>>  '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/temp/build.log'

 * Messages for package x11-apps/intel-gpu-tools-1.7:

 * No Python implementation selected for the build. Please set
 * the PYTHON_SINGLE_TARGET variable in your make.conf to one
 * of the following values:
 * 
 * python3_3 python3_4
 * ERROR: x11-apps/intel-gpu-tools-1.7::gentoo failed (setup phase):
 *   No supported Python implementation in PYTHON_SINGLE_TARGET.
 * 
 * Call stack:
 *                 ebuild.sh, line  93:  Called pkg_setup
 *                 ebuild.sh, line 317:  Called python-single-r1_pkg_setup
 *   python-single-r1.eclass, line 261:  Called python_setup
 *   python-single-r1.eclass, line 251:  Called die
 * The specific snippet of code:
 *              die "No supported Python implementation in PYTHON_SINGLE_TARGET."
 * 
 * If you need support, post the output of `emerge --info '=x11-apps/intel-gpu-tools-1.7::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=x11-apps/intel-gpu-tools-1.7::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/temp/die.env'.
 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/x11-apps/intel-gpu-tools-1.7/work/intel-gpu-tools-1.7'
Comment 1 Alex Xu (Hello71) 2014-07-31 23:14:32 UTC

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