Apple Silicon Erlang 23.2.1 not compiling bcrypt_elixir properly. I think

With bcrypt_elixir you’re not compiling elixir, but C. The error you posted in the github issue on for bcrypt_elixir does indeed suggest there’s some issue with the C related tooling, which may be something elixir_make can adjust for.

Brill. Thanks. I’ll pop over there and see what I can see.

This where I admit I’m an idiot and post the solution for others who didn’t already figure this out.

This was a VSCode problem. Everything was working as intended, but a race condition of a sort was breaking my needed flow.

My VSCode was launched. It’s the intel build, and it’s running the ElixirLS extension (jakebecker version).

I knew I needed to rebuild, so I rm -fr my deps and _build directories.

When VSCode was running in the background, after I deleted the deps directory, it re-fetched the dependencies automatically. The Intel versions, however that works. Rebuilding resulted in the mismatched versions of the bcrypt_nif.so, and Phoenix freaked the hell out when I tried to do any user authentication.

When I completely quit VSCode and built from the terminal after deleting the deps and _build directories, everything fetched and elixir_bcrypt built for the proper architecture.

I didn’t realize that VSCode was using its spawned Intel beam process to correctly fetch those deps according to its architecture. I wanted to share in case someone else has a brain fart like I did. I’ll probably switch to the VSCode insiders arm64 version until the main release gets the Apple Silicon treatment. Or maybe it’s finally time to switch to emacs.

I just ran into this same issue. I build my project in Vagrant but I had left VSCode open looking at the shared folder, so it fetched the host OS NIFs when I was trying to build them inside Vagrant. Learned my lesson, close VSCode when building the release!

I had posted a previous solution which was only a temporary one. The error resurfaced after some time. To get rid of it,

• rm -rf deps _build
• mix deps.get
• mix deps.compile

Do these steps from a separate Silicon terminal instance.

I had the Intel version of NeoVim running. I installed the latest Apple Silicon one, followed the above steps and voila the error went away.

I just ran into this, because I switched to iTerm2 and for whatever reason that defaults to launching in x86 mode.

You can change this in the menu: iTerm2 → Preferences → Profiles → General and change “Login Shell” to “Command” and then enter “arch -arm64 $SHELL”. No idea why this isn’t default…

same issue - with SQLite blowing up with errors on an Apple Silicon (recompiled with elixir 1.13)
Solution for me:

most important part: is to do the following in a vanilla Terminal.app window (not iTerm!)

- rm -rf _build/*
- rm -rf deps/*
- mix deps.get
- mix deps.compile

and poof - compilation errors went away. Can now go back to running iex in an iTerm window no problem.

Is there no way to run vscode in arm mode?

https://code.visualstudio.com

If you’ve never downloaded the universal build, you’ll probably need to do so. I don’t know if the built-in update mechanism will update your x86 build to the universal one. If you’re having problems like this, I suspect VSCode doesn’t change tracks automatically.

This was the solution for me.