-
Notifications
You must be signed in to change notification settings - Fork 3
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
error while loading shared libraries: libhts.so.3: cannot open shared object file: No such file or directory #2
Comments
We are working on getting this into conda so that this isn't necessary, if that can't happen soon we'll include this compile. |
I am facing the same problem, and changing the makefile as recommended by @qiyubio does not work either. Is there any update for this fixing issue? |
Hi, |
Hi, |
hi, I meet the same questions, but i also can't install with conda, when I run |
For now I'm directing people to build from git. I'll try pushing another
release to conda now to see if this fixes the issues.
…On Wed, Jun 12, 2024 at 9:23 AM Junmin ***@***.***> wrote:
Hi, Thanks for the quick reply. I successfully installed vamos with mamba.
hi, I meet the same questions, but i also can't install with conda, when I
run conda install -c bioconda vamos==1.2.0 thre isn't have this package.
and when run conda install -c bioconda vamos, there are many dependencies
questions,but i intsall them with thre requirement.txt as reference.
Can you help me? Thank you !
—
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKPGPROUDU46YZPEFK6IEDZHBYWJAVCNFSM6AAAAABJGWNIDSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGQ2DSNJZHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
While installing vamos with conda/mamba, there is error while trying to run vamos after
make
, the error is: "cannot open shared object file: No such file or directory".ldd vamos is lacking library too. I modified the Makefile accordingly, and now it seems no errors
The text was updated successfully, but these errors were encountered: