Skip to content
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

Document that in some circumstances, trashing ./python/_virtualenv helps with build issues #18775

Open
nox opened this issue Oct 7, 2017 · 4 comments

Comments

@nox
Copy link
Member

@nox nox commented Oct 7, 2017

See #14810 (comment), this is not the first time I hear of this.

@SimonSapin
Copy link
Member

@SimonSapin SimonSapin commented Oct 7, 2017

Should we also make ./mach clean do that as well?

@nox
Copy link
Member Author

@nox nox commented Oct 7, 2017

Maybe that would be for the best indeed. What do you think @jdm?

@jdm
Copy link
Member

@jdm jdm commented Oct 7, 2017

That seems wise.

@philn
Copy link
Contributor

@philn philn commented Oct 18, 2017

The problem with this approach is that mach depends on the virtualenv. Here mach fails early:

Pip failed to execute properly:
Output: 
Error: dyld: Library not loaded: @executable_path/../.Python
  Referenced from: /Users/philn/dev/servo/python/_virtualenv/bin/python2.7
  Reason: image not found
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.