Hi @rhinerunner welcome, how did you install Erlang? PHoenix does not compile any native code so if you’re having segfaults then something is broken with the underlying erlang install.
Hi @benwilson512,
thanks for focusing my attention to this. I installed it via asdf. Now I discarded it and built it from source via brew. (after the regular install didn’t work)
‘brew install --build-from-source erlang’ (25.3.2)
and then
elixir on top of that.
phx_new 1.7.2 is still failing with segmentation faults.
Ensure that when you installed erlang from source you have most of OTP libraries installed, ideally your list of not installed libraries should be:
wx - you need wxwidgets installed;
JInterface - you have to have java installed for this library to compile;
odbc - never used, don’t think it is used anywhere in elixir.
The reason is that if for example you are missing OpenSSL, you won’t be able to compile crypto package from OTP and then you won’t be able to use phoenix because it is using crypto package.
It’s the Erlang ODBC interface. The older SQL Server Ecto provider (mssqlex) uses it and if you need old school access to corporate data repositories you will probably need it.
I’m successfully running Elixir 1.14.3 using asdf, and the same version of Erlang as you. Mac is M1 first gen MacBook Pro, running Ventura 13.3.1 a. I just tested installing the latest Phoenix and it was fine. I do remember fiddling around to get a stable set up when I first started working on my M1 Mac - I can’t recall where I got the recipe, but this article looks familiar:
And then used asdf to bring it to current versions.