-
Notifications
You must be signed in to change notification settings - Fork 14
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
OSX Installation Issues - exited with status error 1 #238
Comments
This looks like a compiler error. OSX uses a different compiler by default than linux distributions. Could you post the version of that? Did you update setuptools and pip before installing? Newer versions of those install pre-compiled binaries where possible which often allows you to bypass compilation problems |
setuptools version: 54.0.0 pip version: pip 21.0.1 Gcc version output:
|
MAVIS is primarily developed for linux, although I have tested it on some OSX environments. The issue here appears to be happening during installing pysam. It doesn't have a pre-compiled binary for your OS and so it attempts to compile it from scratch, but b/c OSX uses a non-standard compiler (clang instead of gcc) it is running into issues |
Python 3.9 is super new so it might not have all the pre-compiled verisons yet, could you try with a lower python version? perhaps 3.8 or 3.7? |
Ok I have been able to reproduce a similar error on ubuntu with python3.9 + pysam so it may not be a OS issue. We will look into this further. @calchoo we froze pysam at 0.15.1 because of breaking changes in 0.15.2, do you remember what those were? have they been fixed? |
Okay great thanks! |
Describe the bug
To Reproduce
Steps to reproduce the behavior:
blat
and create a separate python virtual environment:error.txt
Expected behavior
Complete installation of MAVIS with expected output.
Configuration
If applicable, include the mavis configuration file that was used to run the pipeline
Versions (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: