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

[BUG] anvio installation #2312

Open
UniAlberta opened this issue Jul 26, 2024 · 15 comments
Open

[BUG] anvio installation #2312

UniAlberta opened this issue Jul 26, 2024 · 15 comments

Comments

@UniAlberta
Copy link

Short description of the problem

I get an error for checking if anvio is installed correctly.

anvi'o version

anvio-8

System info

Linux 64, I followed your tutorial https://anvio.org/install/linux/stable/, step by step.

Detailed description of the issue

I`m following https://anvio.org/install/linux/stable/ and things go well to the end of pip install anvio-8.tar.gz. But when I run anvi-self-test --suite mini, it says ImportError: liblzma-51a76f52.so.5.2.4: cannot open shared object file: No such file or directory.

image

@metehaansever
Copy link
Contributor

metehaansever commented Jul 26, 2024

Hello @UniAlberta , Can you share your log file with me so that I can understand the problem?

@UniAlberta
Copy link
Author

UniAlberta commented Jul 26, 2024 via email

@metehaansever
Copy link
Contributor

hey @UniAlberta ,
Your error is most likely caused by the samtools installation and you can find how to fix it in this section of the document: https://anvio.org/install/linux/stable/#issues-related-to-samtools

@UniAlberta
Copy link
Author

UniAlberta commented Jul 26, 2024 via email

@UniAlberta
Copy link
Author

UniAlberta commented Jul 26, 2024 via email

@UniAlberta
Copy link
Author

UniAlberta commented Jul 26, 2024 via email

@ivagljiva
Copy link
Contributor

Since the ImportError is happening for the pysam package, I suspect it is rather an issue with the pysam installation.

Please try to re-install pysam like this: https://anvio.org/install/linux/stable/#issues-with-pysam-installation-using-pip

If the self test still doesn't work, let us know.

@UniAlberta
Copy link
Author

UniAlberta commented Jul 29, 2024 via email

@metehaansever
Copy link
Contributor

@UniAlberta Recently I tried to produce your error on my Linux system but I couldn't. It worked properly on my computer. I can only suggest to create new environment and use mamba instead of conda.

@ivagljiva
Copy link
Contributor

One thing I can suggest is to try the solutions described here for manually linking the shared library file: https://stackoverflow.com/questions/480764/linux-error-while-loading-shared-libraries-cannot-open-shared-object-file-no-s

Basically, if you can find the liblzma-51a76f52.so.5.2.4 file on your computer, then the fix might be as simple as adding the directory in which that file lives to your LD_LIBRARY_PATH environment variable.

If you cannot find that specific file in any of the locations where shared object (.so) files are usually installed by your package manager, but if you can find a different version of the liblzma .so somewhere, sometimes you can fix this sort of issue by symlinking the version you have to the version pysam is looking for, ie running something like ln -s liblzma-51a76f52.so.X.X.X liblzma-51a76f52.so.5.2.4 in the LD_LIBRARY location. But messing with that sort of thing is risky if you don't know what you are doing, so please have caution.

It might be better to ask the Pysam developers for help with this. You can open an issue on their Github: https://github.com/pysam-developers/pysam/issues

@UniAlberta
Copy link
Author

UniAlberta commented Jul 29, 2024 via email

@UniAlberta
Copy link
Author

UniAlberta commented Jul 29, 2024 via email

@meren
Copy link
Member

meren commented Jul 29, 2024

You shouldn't have Python 3.12. Please follow the installation instructions word-by-word :)

@UniAlberta
Copy link
Author

UniAlberta commented Jul 29, 2024 via email

@UniAlberta
Copy link
Author

UniAlberta commented Jul 30, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants