Closed jbadomics closed 8 years ago
Hi Jon,
Unfortunately this makes sense :/
MAC installer contains a lot of pre-compiled programs. Although the operating system is identical, because the compiler was run on a newer version of MAC, some of the CPU specific adjustments at the compiler-level likely resulted in binaries that are incompatible with the previous version of the hardware. At least it seems to be the case with the VBGMM module, which uses scientific libraries that are heavily exploiting the CPU architecture for speed and efficiency.
If you were to recompile VBGMM on that computer and replace the .so file with the new on in the installed application directory you could hack your way out of this.
But for this case I may suggest you to follow the more conventional path to install anvi'o from source.
On the other hand this module is only used by CONCOCT. Which means the rest of the codebase will probably work without any issue, and the only thing you need to do is to use --skip-concoct-binning
every time you use `anvi-merge.
Sorry about this inconvenience.
Best wishes,
Not a problem! Just wanted to bring it to your attention. I'll try building from source and if that proves problematic I'll just bypass CONCOCT as you recommended. Cheers! And thanks for the fast reply!
I am using the anvi'o Mac installer, and I kept getting the same error (entire log posted below) on the lab machine which is a 2009 Mac Pro with 2 quad-core 2.66 GHz Xeon processors running OS X 10.11.4. On my personal laptop (2011 Macbook Pro, 2.7 GHz i7) it installs just fine - also running 10.11.4. Aside from the hardware difference the software configuration is essentially identical.
On the 2009 Mac Pro:
On the 2011 Macbook Pro:
Here's the full error log: