During the configuration phase, the beuild stops with the message: configure:4119: checking Python environment is Mozilla virtualenv Build logs and emerge --info will follow in a few minutes.
Created attachment 380914 [details] emerge --info
Created attachment 380916 [details] configuration log
Created attachment 380918 [details] ebuild log
Add "export SHELL=/bin/sh" to src_configure() to fix this.
I should note -- put it at the top of src_configure().
(In reply to Daniel Robbins from comment #4) > Add "export SHELL=/bin/sh" to src_configure() to fix this. Yes, that fixed it. Many thanks.
I just hit this on a new install-- what is triggering this (ie, why isn't EVERYONE seeing the problem), and should a fix be applied for everyone? Or is there some common configuration problem that needs fixing, independent of spidermonkey itself? The workaround worked for me as well, I put: pre_src_configure() { export SHELL=/bin/sh } ..into /etc/portage/bashrc (temporarily) and it builds successfully.
Good question.. I have yet to reproduce it on my systems. At any rate, adding an export SHELL=/bin/sh is pretty benign, so I've added that in-place. + 30 Sep 2014; Ian Stakenvicius (_AxS_) <axs@gentoo.org> + spidermonkey-24.2.0-r2.ebuild: + Set SHELL to help ./configure ensure python environment is sane, bug 517358 +
(In reply to Ian Stakenvicius from comment #8) > Good question.. I have yet to reproduce it on my systems. At any rate, > adding an export SHELL=/bin/sh is pretty benign, so I've added that in-place. > > + 30 Sep 2014; Ian Stakenvicius (_AxS_) <axs@gentoo.org> > + spidermonkey-24.2.0-r2.ebuild: > + Set SHELL to help ./configure ensure python environment is sane, bug > 517358 > + this is not sane, it should be /bin/bash
