On Mon, Mar 21, 2016 at 11:44:01AM +0000, Hazel Russman wrote:
As far as I can see, it's a problem with python. Config has detected python 2.7 on my system but seems to be trying to use the internal one instead:
Hi. Someone else reported something similar in #crux a few days ago. I've been unable to reproduce it and I dont know if him/her got it going. You might want to try to rebuild python if you havent already done that. The openssl update did silently break some libraries. you could run this: prt-get -fr update $(prt-get dependent openssl)
checking for python2.7... /usr/bin/python2.7 Creating Python environment New python executable in /usr/ports/opt/firefox/work/src/firefox-45.0/firefox-shared/_virtualenv/bin/python2.7 Also creating executable in /usr/ports/opt/firefox/work/src/firefox-45.0/firefox-shared/_virtualenv/bin/python Installing setuptools, pip...
This then leads to a crash: File "/usr/ports/opt/firefox/work/src/firefox-45.0/python/mozbuild/mozbuild/virtualenv.py", line 381, in build self.create() File "/usr/ports/opt/firefox/work/src/firefox-45.0/python/mozbuild/mozbuild/virtualenv.py", line 147, in create raise Exception('Error creating virtualenv.') Exception: Error creating virtualenv.
-- H Russman _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Fredrik Rinnestam