* ERROR: dev-lang/spidermonkey-45.0.2::gentoo failed (setup phase): * No supported Python implementation installed. * * Call stack: * ebuild.sh, line 115: Called pkg_setup ----------------------------------------------------------------- This is an unstable amd64 chroot image (named hardened_20170217-144156) at a hardened host acting as a tinderbox. ----------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * [2] x86_64-pc-linux-gnu-5.4.0-hardenednopie [3] x86_64-pc-linux-gnu-5.4.0-hardenednopiessp [4] x86_64-pc-linux-gnu-5.4.0-hardenednossp [5] x86_64-pc-linux-gnu-5.4.0-vanilla Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python3.5 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby21 (with Rubygems) * java-config: The following VMs are available for generation-2:
Created attachment 465484 [details] emerge-info.txt
Created attachment 465486 [details] dev-lang:spidermonkey-45.0.2:20170228-052953.log
Created attachment 465488 [details] die.env
Created attachment 465490 [details] emerge-history.txt
Created attachment 465492 [details] etc.portage.tbz2
Any thoughts on why this is? python-any-r1 is inherited, PYTHON_COMPAT=( python2_7 ) is specified, $PYTHON_DEPS is in DEPEND, and python-any-r1_pkg_setup is called as the last item of moz_pkg-setup just like it is for firefox et. al.. So far as I am aware, that checks all the boxes...?
Also, could you force a check of spidermonkey-38.2.1_rc0 to see if it fails the same way?
* Package: dev-lang/spidermonkey-38.2.1_rc0 * Repository: gentoo * Maintainer: mozilla@gentoo.org * USE: abi_x86_64 amd64 elibc_glibc jit kernel_linux system-icu userland_GNU * FEATURES: ccache preserve-libs sandbox userpriv usersandbox * No Python implementation found for the build. This is usually * a bug in the ebuild. Please report it to bugs.gentoo.org * along with the build log.
* Call stack: * ebuild.sh, line 115: Called pkg_setup * spidermonkey-38.2.1_rc0.ebuild, line 40: Called moz_pkgsetup * mozcoreconf-v4.eclass, line 115: Called python-any-r1_pkg_setup * python-any-r1.eclass, line 343: Called python_setup * python-any-r1.eclass, line 331: Called die * The specific snippet of code: * die "No supported Python implementation installed."
eclass-debug.log from anyone who could repro, please.
Oh, nevermind. The original issue was that the ebuild was setting a different value of PYTHON_REQ_USE, which then the mozcoreconf eclass overrode. The repeat inherit guard caused PYTHON_DEPS not to be redefined, so PYTHON_DEPS had the old value, while python_setup() logic used the new. As a result, smaller set of PYTHON_REQ_USE was enforced by deps while python_setup() bailed out because of mismatched flags.
(In reply to Michał Górny from comment #10) just curious how to achieve that file ? Is it just somewhere under /var/tmp/portage/ ?
(In reply to Toralf Förster from comment #12) > (In reply to Michał Górny from comment #10) > just curious how to achieve that file ? Is it just somewhere under > /var/tmp/portage/ ? Yes, in the temp/ subdirectory.
If you feel I have closed your bug and it is still a current issue, please reopen and update it completely. We will not work bugs that have no ebuild in tree any longer or can not be reproduced with a current system. Thank You for your support and understanding The Mozilla Team
