-
Notifications
You must be signed in to change notification settings - Fork 37
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
run issue #10
Comments
Thank you for reporting this.
I also just try testing nucleus 0.5.8, which I suspect also didn't work on CentOS7. We'll have to think about what to do with this. I'll keep this open for now. |
Thanks for your reply. I also got your problem. And after installing bzip2 in my conda environment this error was gone. |
Hi @MartinPippel ,
After that, I'm also seeing: "`GLIBC_2.23' not found". Actually, this reminded me that this is probably part of Nucleus - I tested Nucleus 0.5.8 (which DeepConsensus builds on), and we have the same issue. CentOS7 has an older GLIBC, and that's why we're having the issue. I think it is possible for us to build Nucleus and DeepConsensus in a way that is manylinux2010 compliant, and hopefully resolve this issue. I will add this to our list of tasks, but I don't know for sure when we can prioritize this. Another approach we could try to take is to use Docker (more like what we did for DeepVariant) instead of pip wheels. Either approach will take some time for us. @MartinPippel , given that I've filed an internal issue to track this, I'll close this for now. But please feel free to add more here. |
I am experiencing the same issue on CentOS7, Python 3.6.9, conda etc. All of the notable details appear to be the same (including bzip2 sub-issue). |
I think this is because the google-nucleus binary by pip was built under /lib64/libm.so.6: version 'GLIBC_2.23'. |
I have some issues to run deepconsensus on our Centos 7 linux cluster. Any advice would be highly appreciated.
I also got the following two errors during the installation:
Thanks,
Martin
The text was updated successfully, but these errors were encountered: