helium/blockchain-node

unable to build

Closed this issue · 7 comments

terrancewong commented
  • Debian testing
% make
./rebar3 compile
===> Verifying dependencies...
===> Fetching blockchain (from {git,"https://github.com/helium/blockchain-core.git",
                      {ref,"b4bacdaa62f12f4c109f8349d74efce4cc6c5a5d"}})
escript: exception error: undefined function erlang:get_stacktrace/0
  in function  rebar3:main/1 (/home/runner/work/rebar3/rebar3/src/rebar3.erl, line 72)
  in call from escript:run/2 (escript.erl, line 750)
  in call from escript:start/1 (escript.erl, line 277)
  in call from init:start_em/1 
  in call from init:do_boot/3 
make: *** [Makefile:17: compile] Error 127

function erlang:get_stacktrace/0 is removed from OTP 24

and https://packages.erlang-solutions.com/erlang-solutions_2.0_all.deb is an empty deb

is compiling entire OTP 23 the only way?

madninja commented

No, install an erlang 23 version from an apt repository as specified here: https://github.com/helium/blockchain-node#installing-ubuntu-required-packages

terrancewong commented

The problem is erlang-solutions_2.0_all.deb is very out-dated. only has code names for Ubuntu up to 19.04 "disco" and Debian up to 9 "stretch".

a .list must be manually created under /etc/apt/sources.list.d/

deb https://packages.erlang-solutions.com/ubuntu stretch contrib

or

deb https://packages.erlang-solutions.com/ubuntu focal contrib

for 3 years old new OSes.

madninja commented

you are right.. the esl source list is apparently quite out of date. Would you be willing to update the README to reflect installation instructions as needed for newer versions of Debian/Ubuntu?

terrancewong commented

and, OTP 22 has some unmet deps with Debian testing. and OTP 23 works fine in ubuntu 21.04

madninja commented

I believe blockchain-node should work fine with OTP 23

terrancewong commented

OTP 24 just has a deprecated erlang:get_stacktrace/0, how about make it work :-D

madninja commented

OTP 24 just has a deprecated erlang:get_stacktrace/0, how about make it work :-D

at some point yes.. just using OTP 24 will fail in a number of places across core and node. And yes we know :-)

In the meantime you can use OTP 23