You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In https://github.com/tonyrog/cl/archive/cl-1.2.1.tar.gz (it can also be present in 1.2 as well, I did not check), the file src/cl.app.src has the statement {vsn, git} rather than {vsn, "1.2.1"}. This results in the following error on a compilation attempt:
==> cl-cl-1.2.1 (compile)
Compiled src/clu.erl
Compiled src/cl13.erl
Compiled src/cl12.erl
Compiled src/cl11.erl
Compiled src/cl10.erl
Compiled src/cl.erl
Compiling c_src/cl_nif.c
Compiling c_src/cl_hash.c
ERROR: sh(git describe --always --tags)
failed with return code 128 and the following output:
fatal: Not a git repository (or any parent up to mount point /var/tmp/portage)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
ERROR: compile failed while processing /var/tmp/portage/dev-libs/erlang-cl-1.2.1/work/cl-cl-1.2.1: rebar_abort
Changing for {vsn, "1.2.1"} fixes the issue.
The text was updated successfully, but these errors were encountered:
In https://github.com/tonyrog/cl/archive/cl-1.2.1.tar.gz (it can also be present in 1.2 as well, I did not check), the file src/cl.app.src has the statement {vsn, git} rather than {vsn, "1.2.1"}. This results in the following error on a compilation attempt:
==> cl-cl-1.2.1 (compile)
Compiled src/clu.erl
Compiled src/cl13.erl
Compiled src/cl12.erl
Compiled src/cl11.erl
Compiled src/cl10.erl
Compiled src/cl.erl
Compiling c_src/cl_nif.c
Compiling c_src/cl_hash.c
ERROR: sh(git describe --always --tags)
failed with return code 128 and the following output:
fatal: Not a git repository (or any parent up to mount point /var/tmp/portage)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
ERROR: compile failed while processing /var/tmp/portage/dev-libs/erlang-cl-1.2.1/work/cl-cl-1.2.1: rebar_abort
Changing for {vsn, "1.2.1"} fixes the issue.
The text was updated successfully, but these errors were encountered: