Iulian7
Hi guys,
I have an Erlang dependency which does not compile with mix but compiles fine with rebar3. The output when compiling with DEBUG=1 is:
...
===> Building escript...
===> Creating escript file /Users/iulian/elixir/riak/deps/cuttlefish/_build/default/bin/cuttlefish
===> processing <<"cuttlefish">>
===> new deps of <<"cuttlefish">> found to be []
===> processing <<"getopt">>
===> Uncaught error in rebar_core. Run with DEBUG=1 to see stacktrace or consult rebar3.crashdump
===> Uncaught error: {badmatch,error}
===> Stack trace to the error location:
[{rebar_prv_escriptize,find_deps_of_deps,3,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_prv_escriptize.erl"},
{line,246}]},
{rebar_prv_escriptize,find_deps,2,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_prv_escriptize.erl"},
{line,240}]},
{rebar_prv_escriptize,escriptize,2,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_prv_escriptize.erl"},
{line,104}]},
{rebar_prv_escriptize,do,1,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_prv_escriptize.erl"},
{line,80}]},
{rebar_core,do,2,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_core.erl"},
{line,153}]},
{rebar_hooks,run_provider_hooks_,6,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_hooks.erl"},
{line,49}]},
{rebar_hooks,run_all_hooks,6,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_hooks.erl"},
{line,16}]},
{rebar_prv_compile,compile,3,
[{file,"/home/tristan/Devel/rebar3/_build/default/lib/rebar/src/rebar_prv_compile.erl"},
{line,129}]}]
...
I am running Elixir 1.4.5, Erlang/OTP 20 on macOS Sierra. I also made sure the rebar3 mix uses is the correct version using mix local.rebar rebar3. The rebar3 version is 3.4.2.
Any help would be much appreciated!
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
Getopt uses legacy rebar, try setting manager rebar for it.
Iulian7
I set
{:getopt, "~> 0.8.2", manager: :rebar3, override: true}, however I still get the same error.NobbZ
I said
rebar, notrebar3.Iulian7
Unfortunately same situation. I also made sure to update mix local.rebar rebar.
Again this only happens if I compile with mix. If I compile the dependency with
rebar3it compiles.EDIT: I now have
{:getopt, "~> 0.8.2", manager: :rebar, override: true}Iulian7
If it helps, the dependency is riak_core_ng | Hex which in turn depends on cuttlefish | Hex (the culprit in this discussion).
georosz
I had similar, but not the same issue before, also I use linux not OSX
I managed to solve it by reinstalling erlang and elixir.
https://forum.elixirforum.com/t/cannot-compile-unicode-util-compat/6724
Iulian7
Well I also tried that but it didn’t work. It’s very frustrating now. If I compile
getoptwith mix usingmix deps.compile getoptit works. If I compile them individually it works except forcuttlefishwhich gives that error. This is so strange.I again tried to compile the whole thing with
rebar3and it works fine. I even compiled with~/.mix/rebar3for sanity check to make suremixis not using some strange version.peerreynders
Ok - grasping at straws here:
On Digital Ocean/Ubuntu there seems to be an emerging pattern that compiling certain applications with
rebar3throughmixcan run into trouble in a memory constrained environment (512 MB RAM).https://github.com/elixir-lang/elixir/issues/3857#issuecomment-220746100
Now, I haven’t seen anything comparable for OS X - but it may be worth firing up Activity Monitor and watching the “Memory” tab to see what is happening to the physical memory consumption during compilation:
Iulian7
Interesting. I observed the memory usage. It doesn’t really go up and there is no swapping. It is worth noting I have 16GB of RAM. The usage is constant at about 8GB.
This is also followed in this issue: Problems compiling (warnings_as_errors) · Issue #23 · Kyorai/riak_core · GitHub.
peerreynders
Well, that rule’s that out.
Though I wonder if there is a way to see exactly what information is passing from
mixtorebar3- in caserebar3is simply choking on some “bad (truncated?) configuration information”.