Fl4m3Ph03n1x
Cannot install erlang 20.3.8.23
Background
I am trying to install erlang 20.3.8.23 via asdf on my droplet so I can use an elixir server for VIM (using ALE), but unfortunately the installation is failing.
Problem
10624 CC x86_64-unknown-linux-gnu/wxe_driver.o
10625 CC x86_64-unknown-linux-gnu/wxe_ps_init.o
10626 CXX x86_64-unknown-linux-gnu/wxe_main.o
10627 CXX x86_64-unknown-linux-gnu/wxe_impl.o
10628 CXX x86_64-unknown-linux-gnu/wxe_helpers.o
10629 CXX x86_64-unknown-linux-gnu/wxe_callback_impl.o
10630 CXX x86_64-unknown-linux-gnu/wxe_return.o
10631 CXX x86_64-unknown-linux-gnu/wxe_gl.o
10632 CXX x86_64-unknown-linux-gnu/wxe_funcs.o
10633
10634 cc1plus: out of memory allocating 65536 bytes after a total of 364257280 bytes
10635 Makefile:156: recipe for target 'x86_64-unknown-linux-gnu/wxe_funcs.o' failed
10636 make[3]: *** [x86_64-unknown-linux-gnu/wxe_funcs.o] Error 1
10637 make[3]: Leaving directory '/root/.asdf/plugins/erlang/kerl-home/builds/asdf_20.3.8.23/otp_src_20.3.8.23/lib/wx/c _src'
10638 /root/.asdf/plugins/erlang/kerl-home/builds/asdf_20.3.8.23/otp_src_20.3.8.23/make/otp_subdir.mk:29: recipe for ta rget 'opt' failed
10639 make[2]: *** [opt] Error 2
I understand from this log that this fails because my droplet doesn’t have enough memory. This is rather astonishing to me, as I have installed erlang 22.1 in the same machine and I didn’t have the same issue.
The other thing that jumps to my eye is the x86_64-unknown-linux-gnu. Why can’t the install figure out what version of linux I have? (is this even important?)
My droplet has the following OS:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Codename: bionic
It has 1GB of RAM and 25GB of disk.
How can I fix this issue?
Marked As Solved
outlog
you can add swap so the server can “survive” the compile…
maybe erlang 22.1 is more effective during compile… did you install that using asdf as well?
after a total of 364257280 bytes
that is only ~350 mb - is something else using memory? (postgres? running beam?)
Also Liked
NobbZ
I tried again, I resized my 5 USD droplet to a 10 USD one, booted into it, run some random commands, powered down and resized back to a 5 USD one…
And now I will destroy this testmachine again before I get billed to much for it.
And its just as I said, “Resize CPU and RAM only” has to be choosen. For me the option with disk size included was preselected.
Fl4m3Ph03n1x
I have resized my droplet and compiled erlang. It worked. My droplet now has 4gb of RAM and costs 4x as much.
Initially I didn’t think this was going to be an issue, after all, this is just a temporary scale up (I thought).
Unfortunately for me, as I later found out, I’m not able to downsize the droplet as the official article mentioned. I’m stuck with a droplet that will cost me 4x as much and the only thing I can do is to scp the files I want to a smaller instance, which is incredibly disappointing.
Doing so will not only take hours(which I pay for, obviously) it also requires me to know where asdf places all the releases and scp them manually.
In hindsight, resizing the droplet was a terrible mistake, I should have simply created a 3GB swap partition and let the SSD drive take the heat.
I hope my experience helps someone in the future!
NobbZ
The droplet in question is his “local” as the computer he got is suited even worse for developing elixir/Erlang. At least that’s how I understood this thread and an earlier one.







