-
Notifications
You must be signed in to change notification settings - Fork 80
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
Problem with kmer-db installation #741
Comments
Is this happening on the latest version of SqueezeMeta? |
/home/gho/miniconda3/envs/SqueezeMeta/bin/kmer-db
This is the latest version, yes? Output of ...As in my kmer-db issues post, I have replaced this kmer-db with three different versions, all getting the same error. Currently the kmer-db in my current installation is actually a copy from kmer-db v. 1.7.2 (15.01.2020), which works on my colleagues' installation. (I was getting desperate, I spent almost a whole work week trying to install SqueezeMeta and I think this is the last thing in my way.) Before replacing it with their version, I received the error message in linked above. Now I get
(EDIT: sorry I accidentally closed this! I new to github!) |
Good news is that you may not need kmer-db at all for running SqueezeMeta (unless you plan to use the seqmerge mode).
|
Same message with the above... "Illegal instruction" Edit: It seems if I ssh onto a different server dedicated to jobs requiring larger memory, it works! OS on the server which works: Linux-4.9.0-19-amd64-x86_64-with-glibc2.24 I don't know enough about Linux to know why one works but not the other, but I guess this issue can be closed. |
As I suspected the problem was related to how the kmer-db from conda was compiled. |
After running
test_install.pl
everything goes fine untilkmer-db -h
.I opened a separate issue on their github page , but my colleague suggested I crosspost it here since you are more responsive.
Basically, no matter how I install
kmer-db
, I get the "Illegal instruction" error.Any clues? More info is found in the kmer-db issue thread, but I am running on linux-64 (Debian GNU/Linux 10 (Buster))
The text was updated successfully, but these errors were encountered: