link
- (Mix) Could not compile dependency :chatterbox, “/home/user/.mix/rebar3 bare compile --paths “/home/user/Documents/signalbroker/signal_server/_build/dev/lib/*/ebin”” command failed. You can recompile this dependency with “mix deps.compile chatterbox”, update it with “mix deps.update chatterbox” or clean it with “mix deps.clean chatterbox”
I have tried all the three suggestions, still get the same error.
I use ubuntu 18, 64 bit
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #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.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
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
Probably because they have warnings_as_errors in their rebar default profile… Please checkout the repository in the exact version you want to use in your project, try to build and then file a bug report in their GitHub repository, asking to move the warnings_as_errors setting as well, as it breaks projects that depend on it.
link
How do I know which exact version I need in my project?
NobbZ
mix deps | grep chatterboxIIRC.link
This is what I get from the command you sent. I guess it gives me which version I have, not which version I should have?
NobbZ
It looks like you have a git dependency, not constraint by any branch/tag/commit, so you get whatever HEAD was on the first deps.get, it should be fine to simply try with HEAD from the repo and create the issue based on that.
NobbZ
PS: they are using
gen_fsmwhich is a not trivial to fix issue, depending on which versions of OTP they want to support.Easiest for now should be to fork/vendor a version that has the
warnings_as_errorsremoved from the config.link
Thanks, removing the
warnings_as_errorsfixed the problem.NobbZ
Have you made them aware of the problems they are causing by that setting?
tristan
I’m fine with removing it from the default profile. Please send a PR to chatterbox and I’ll merge it.
Also note that in the latest gen_fsm has been replaced by gen_statem.
(I just realized you are using a fork of chatterbox… Maybe tony612 would be willing to upgrade his fork to the latest upstream also).
link
No, how do I do that?