-
Notifications
You must be signed in to change notification settings - Fork 121
Build fails on Arch Linux unless PYTHON env. variable is set #129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This happened for me as well, thanks for sharing your solution. Worked great! |
marmistrz
added a commit
to marmistrz/mozjs
that referenced
this issue
Feb 26, 2018
If python2 seems to be a valid Python 2 interpreter, the configure script will use it. Otherwise, it will fall back to python, as previously. We also bump the crate version so that this change can be propagated further the dependency tree. Closes servo#129.
marmistrz
added a commit
to marmistrz/mozjs
that referenced
this issue
Feb 26, 2018
If python2 seems to be a valid Python 2 interpreter, the configure script will use it. Otherwise, it will fall back to python, as previously. We also bump the crate version so that this change can be propagated further the dependency tree. Closes servo#129.
bors-servo
pushed a commit
that referenced
this issue
Feb 26, 2018
Use python2 for the build whenever possible and bump the version. If python2 seems to be a valid Python 2 interpreter, the configure script will use it. Otherwise, it will fall back to python, as previously. We also bump the crate version so that this change can be propagated further the dependency tree. Closes #129. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/mozjs/132) <!-- Reviewable:end -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
cargo build
bails out withNo such error occurs if the invocation is
PYTHON=python2 cargo build
.The text was updated successfully, but these errors were encountered: