garrison
Just ran into some trouble updating elixir with brew so I thought I’d provide a quick writeup since I didn’t see anything else while searching.
I was upgrading elixir with brew upgrade and received an error claiming that wxwidgets@3.2 could not be linked, which interrupted the upgrade. A brew doctor check indeed showed it was unlinked.
Some brief spelunking showed that the erlang package was switched from wxwidgets to wxwidgets@3.2 for whatever reason.
Unfortunately it appears that these packages conflict during linking, and brew is not smart enough to uninstall wxwidgets (which was at the time actually at 3.2) before installing wxwidgets@3.2.
I first tried upgrading wxwidgets, which inadvertently upgraded erlang and elixir (brew moment), and surprisingly that upgrade completed successfully, but wxwidgets@3.2 still wasn’t linked. This seemed like a bad state to be in (presumably they pinned the version for a reason).
I tried brew link wxwidgets@3.2 thinking maybe it wouldn’t conflict now that wxwidgets was at 3.3, but apparently the paths still conflicted. I then tried uninstalling wxwidgets, but brew claimed that it was still required by elixir (but not erlang?!), which was a lie (elixir only depends on erlang). I then tried forcibly uninstalling wxwidgets, which succeeded.
I was going to then attempt brew link again, but at this point I realized I was wasting my time and just uninstalled elixir (which cleared out the deps) and reinstalled it from scratch, and the dependency resolution proceeded correctly that time (wxwidgets was not installed).
TL;DR brew uninstall elixir && brew install elixir
Where Next?
Trending in Guides/Tuts
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #ai
- #elixirconf-us
- #blog-post
- #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.
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.
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.
**Building the future of software with AI, trust, and human connection.**
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 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
adamu
For me using
brewandkerlI was getting this error when attempting to start observer:The erlang docs currently state that 3.3 is experimental, so to install 3.2 with brew I had to:
brew uninstall wxwidgetsbrew install wxwidgets@3.2whereis wx-config-3.2and add this toKERL_CONFIGURE_OPTIONS:--with-wx-config=/opt/homebrew/bin/wx-config-3.2Then rebuild erlang.
garrison
Ah, well I guess that’s why they pinned it!