-
Notifications
You must be signed in to change notification settings - Fork 20
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
Install error #13
Comments
Hi @a00101 , This issue seems to do with different versions of the calcRoiCovg library. If you look closely at calcRoiCovg's Makefile, it will tell you what environment variable you should be setting. From this version of calcRoiCovg, for example, it is evident that the environment variable for Samtools directory should be called
Solution: try to export the following; one of them should work (also change the path of course):
Best, Felix |
Hi, Using the guide I overcame the fist error with joinx about StreamLineSource.cpp. Please let me know of the following issue. ------------Error message--- |
Hi @rajkump, As far as I can tell, the issue is that C++ used to allow you to evaluate an istream as bool and now it does not. However, based on this page: https://stackoverflow.com/questions/41564040/evaluating-stream-operator-as-boolean It looks like !(istream) still evaluates as a bool (admittedly with reversed values). I therefore got joinx to compile by editing test/lib/fileformats/TestVcfEntry.cpp to replace the two lines that look like
to instead
Hope that helps! |
Hello @jasonptm I also had a same error as @rajkump had, and I also changed two lines as you recommended. However, it still returns same error. I am working on Ubuntu 18.10 and only make step of JoinX occurs those errors. The error message is as below; In file included from /home/audrey/joinx/build/vendor/src/gtest160/include/gtest/gtest.h:57:0, |
at directory of samtools1.9
export SAMDIR=$PWD
cd ../calcRoiCovg/
make
Please define environment variable SAMDIR to point to your samtools libraries
what should I do that?
Thanks
The text was updated successfully, but these errors were encountered: