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
xtract command: can not execute binary file #100
Comments
This sounds like a packaging error with conda, the xtract program used to be written in perl where the architecture did not matter. The latest version is written in GO and it seems it conflicts with Catalina. This may take a bit to resolve at the packaging level, for now you can do a:
to use the previous working version |
Another quick and dirty fix is to do:
this will rewrite your copy of xtract with the correct version |
Great, thank you very much...the last "quick and dirty fix" using the curl worked (and tested from the example of the Handbook section). Will need to learn more about xtract to check other things in the future, but looks like it's working. Sincerely NK |
The packaging error has been corrected in bioconda. New installations should now work. |
Hello, I have followed all the steps in the handbook guide (downloaded everything new on Jan 31 2020), activated the bioinfo environment, installed the components according to the Handbook website, and checked that the paths are correct. The entrez-direct utilities all work fine after installation (esearch, efetch, etc etc), excpet for the xtract command. I ran an update on the entrez-direct package as well and still get the same error. Is there something that I am missing? I have been looking through some of the other forums and there may be an issue with the file architecture, and when I did: $file xtract, I got the following details:
xtract: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=PFsOSZjKx4OrmHD5Bwmu/zGzoYroadHkNaH3o3Csi/zAL6g_Cnn3klIv6NBUiS/swsm8RmHeMFF5ZTvvS-e, not stripped
I don't know what all that means, but it appears as it's an executable file, but apparently it can not run....
I am running on macOS Catalina, Intel core i9
Thanks!
NK
The text was updated successfully, but these errors were encountered: