On Wed, Nov 25, 2020 at 08:31:56PM -0700, Jonathan Matthew wrote:
> CVSROOT: /cvs
> Module name: ports
> Changes by: [email protected] 2020/11/25 20:31:56
> Log message:
> Import rebar3-3.13.2 - "the official build tool for Erlang"
> ok jasper@
> Status:
> Vendor Tag: jmatthew
> Release Tags: jmatthew_20201126
> N ports/devel/rebar3/Makefile
> N ports/devel/rebar3/distinfo
> N ports/devel/rebar3/patches/patch-bootstrap
> N ports/devel/rebar3/patches/patch-src_rebar_prv_escriptize_erl
> N
> ports/devel/rebar3/patches/patch-_build_default_lib_relx_priv_templates_bin
> N ports/devel/rebar3/patches/patch-rebar_config
> N
> ports/devel/rebar3/patches/patch-_build_default_lib_relx_priv_templates_extended_bin
> N ports/devel/rebar3/pkg/DESCR
> N ports/devel/rebar3/pkg/PLIST
> No conflicts created by this import
This fails on sparc64 with:
escript: exception throw: {error,
{rebar_file_utils,
{bad_term_file,"/root/.config/rebar3/rebar.config",
eacces}}}
in function rebar_file_utils:try_consult/1 (src/rebar_file_utils.erl, line 67
)
in call from rebar_config:consult_file/1 (src/rebar_config.erl, line 212)
in call from rebar_utils:get_http_vars/1 (src/rebar_utils.erl, line 910)
in call from rebar_utils:set_httpc_options/0 (src/rebar_utils.erl, line 920)
in call from rebar3:init_config/0 (src/rebar3.erl, line 201)
in call from rebar3:run/1 (src/rebar3.erl, line 100)
===> Exiting devel/rebar3 with an error
I don't see the package available for amd64 on any mirrors either. I suspect
this doesn't build on any arch.
--Kurt
