search

sonic-pi-net / sonic-pi

Code. Music. Live.
https://sonic-pi.net
Other
10.78k stars 922 forks source link

4.5.1 build for 486 Ubuntu 24.04 #3420

Open sdcurtin opened 3 weeks ago

sdcurtin commented 3 weeks ago

Has anyone built Sonic Pi 4.5.1 on/for 486 Ubuntu 24.04? I have a new 8gb Raspi 5 that I have Ubuntu 22 running on, and the new pipewire audio is so much more reliable and cooperates with the rest of the system much better than jack. I’d like to code as well on my 486 machines running the same OS. Just updated my Ubuntu 22 486 to 24.04 and ran ./linux-build-all.sh, it got almost all the way through with the following issue, any ideas for a fix? I verified I have the current Erlang. Compiling Erlang/Elixir files... 15:03:14.349 [error] Task #PID<0.111.0> started from #PID<0.96.0> terminating (MatchError) no match of right hand side value: {:error, {:ssl, {'no such file or directory', 'ssl.app'}}} (mix 1.14.2) lib/mix/utils.ex:647: Mix.Utils.read_httpc/1 (mix 1.14.2) lib/mix/utils.ex:579: anonymous fn/2 in Mix.Utils.read_path/2 (elixir 1.14.2) lib/task/supervised.ex:89: Task.Supervised.invoke_mfa/2 (elixir 1.14.2) lib/task/supervised.ex:34: Task. Supervised.reply/4 (stdlib 4.1.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3 Function: #Function<5.4650298/0 in Mix.Utils.read_path/2> Args: [] (EXIT from #PID<0.96.0>) an exception was raised: (MatchError) no match of right hand side value: {:error, {:ssl, {'no such file or directory', 'ssl.app'}}} (mix 1.14.2) lib/mix/utils.ex:647: Mix.Utils.read_httpc/1 (mix 1.14.2) lib/mix/utils.ex:579: anonymous fn/2 in Mix.Utils.read_path/2 (elixir 1.14.2) lib/task/supervised.ex:89: Task. Supervised.invoke_mfa/2 (elixir 1.14.2) lib/task/supervised.ex:34: Task.Supervised.reply/4 (stdlib 4.1.1) proc_lib.erl:240: :proc_lib.init_p_do_apply/3

sdcurtin commented 3 weeks ago

Here's a clue: The error message "no match of right hand side value: {:error, {:ssl, {'no such file or directory', 'ssl.app'}}}" can occur when an application is not prepared to serve requests over SSL. To fix this, you can: Add a key file and certificate file from a certificate authority Set the paths to the files in your environment variables Create a new https: key for your endpoint The configuration will include: A keyword list of port, Path to the key file, and Path to the cert (pem) file.