-
Notifications
You must be signed in to change notification settings - Fork 68
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
faToTwoBit: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file #110
Comments
FusionCatcher installation thru conda is new and I perform tests right now. It might be that the issue is related regarding the the conda channels are in wrong order? How does your |
Ah, I've seen this problem many times. A dirty and quick workaround is to create a symlink. ln -s /lib/x86_64-linux-gnu/libssl.so.1 /lib/x86_64-linux-gnu/libssl.so.1.0.0 |
Thanks very much - I'll try this! |
matq007 has the right idea, but it has to be inside the conda env. Assuming your env name is 'fusioncatcher':
|
This is still not fixed. I installed fusioncatcher now with conda and am still getting the problem. The solution by @ScubaChris worked to solve it, but should be integrated into the conda install solution. I did find the similar issue and solution here: PacificBiosciences/pbbioconda#85 |
Hey @pbiology I am using |
I seem to be getting some strange results. I get different conda environments depending on how I create them.
Generating the environment from the environment.yml file gives me errors while running the fusion-catcher pipeline This might be outside of the scope for fusioncatcher to fix, but I'd thought I'd mention it. |
Hello,
I am fairly new to this so apologies if this is a simple error on my part!
I downloaded fusioncatcher via conda and have been running it on both test samples from the manuel and some downloaded GEO RNAseq data. In both cases there is an error at step 369 which means I do not reach the final list of transcripts (see below). The preliminary list looks ok.
Very grateful for your help and many thanks!
The text was updated successfully, but these errors were encountered: