Closed nickdichev-firework closed 4 weeks ago
When you run Elixir what value do you get for:
:erlang.system_info(:system_architecture)
Your GCC target is x86, is it running with Rosetta?
Note if you continue to have issues, you can also force XLA to use a specific archive by setting XLA_ARCHIVE_URL
, but it should auto detect the correct system based on your system info
Thanks for putting me on the right track, I hadn't noticed that until today. Something strange is going on with my nix environment, will have to poke at that.
I recently started running into trouble with exla on my mac machines. I am using nix to manage my development environment, however, I am able to have the dep correctly pull the precompiled xla on my linux servers using the same nix inputs.
Here is the exla output:
one thing I immediately notice is odd is that it pulled an x86 xla tarball, but this system is a m1 pro, however, I am having the same problem on my x86 mac as well (although I dont have access to it right now to check what tarball is being used).
on this system:
however I noticed my linux env has gcc 13, which I started explicitly pinning in my nix env. There are still problems compiling the exla dependency on this setup but they are different.
Any ideas? Let me know if there are any other details you could use. Thanks in advance!