grisp / grisp/mix_grisp

Erlexec compile error in mix grisp.deploy

Open
#13 2 comments 0 reactions 1 assignee View on GitHub

@sylane is already working on this.

Since Sep 16, 2024.

Dominant language
Elixir
Stars
6
Forks
6
Avg merge
1d 8h
Merged PRs (30d)
3

Description

In grisp_tools 2.7.0 erlexec is introduced in the dependency tree, but somehow mix cannot build it.

mix grisp.deploy                                                                                                                                                   
===> Error reading file /Users/***/Desktop/grisp/testex/_build/dev/lib/erlexec/mix.rebar.config: 8: cannot translate from UTF-8
** (Mix) Could not compile dependency :erlexec, "/Users/***/.asdf/installs/elixir/1.16.3-otp-26/.mix/elixir/1-16/rebar3 bare compile --paths /Users/***/Desktop/grisp/testex/_build/dev/lib/*/ebin" command failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile erlexec --force", update it with "mix deps.update erlexec" or clean it with "mix deps.clean erlexec"

This is the generated file _build/dev/lib/erlexec/mix.rebar.config

{hex,[{doc,ex_doc}]}.
{ex_doc,[{extras,[{"README.md",#{title => "Overview"}},
                  {"LICENSE",#{title => "License"}}]},
         {main,"README.md"},
         {authors,["Serge Aleynikov"]},
         {source_url,"https://github.com/saleyn/erlexec"}]}.
{erl_opts,[debug_info,warn_export_all]}.
{edoc_opts,[{def,{vsn,"fatal: .git non � un repository Git (n� lo � alcuna delle directory genitrici)"}}]}.
{plugins,[rebar3_hex,rebar3_ex_doc]}.
{post_hooks,[{"(freebsd|netbsd|openbsd)",clean,"gmake -C c_src clean"},
             {"(linux|darwin|solaris)",clean,"make -C c_src clean"}]}.
{pre_hooks,[{"(freebsd|netbsd|openbsd)",compile,"gmake -C c_src"},
            {"(linux|darwin|solaris)",compile,"make -C c_src"}]}.
{overrides,[]}.

Line 8 is giving error, why is there that edoc_opts list? the vsn string is a git error so no wonder it fails...

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.