Currently, the anaconda installer-installed python's platform.machine() returns x86_64, because anaconda has only a x86_64 bootloader. This causes a problem when trying to link arm64 libraries installed via brew.
This means that in order to compile locally, users need to use brew's python or their system python. This is suboptimal.
Previously, this worked on my machine because the brew-installed libraries were the x86_64 versions, because my shell was confused. Fixing my shell installed the arm64 versions, which no longer worked with conda's python.
This is likely related to #167 . I'm guessing that the Github runners install the x86_64 versions of the libraries. Then, on some M1 Macs, brew install libomp installs the arm64 versions of those libraries. Can we somehow fix this? Perhaps by compiling on M1 Mac Github runners when they're available? Or by having users that run into the bug install the x86_64 versions of the libraries?
Currently, the anaconda installer-installed python's
platform.machine()returnsx86_64, because anaconda has only ax86_64bootloader. This causes a problem when trying to linkarm64libraries installed viabrew.This means that in order to compile locally, users need to use
brew'spythonor their systempython. This is suboptimal.Previously, this worked on my machine because the
brew-installed libraries were thex86_64versions, because my shell was confused. Fixing my shell installed thearm64versions, which no longer worked withconda'spython.This is likely related to #167 . I'm guessing that the Github runners install the
x86_64versions of the libraries. Then, on some M1 Macs,brew install libompinstalls thearm64versions of those libraries. Can we somehow fix this? Perhaps by compiling on M1 Mac Github runners when they're available? Or by having users that run into the bug install thex86_64versions of the libraries?