bend
I’m a beginner, using Linux MInt 18.3 Cinnamon. I installed elixir with apt, but it only found version 1.1, and I’d like to use the newest version, but I have been having trouble. From memory here is what happened:
Tried to install elixir 1.8.2 from source. Got error about Erlang (I had version 18).
Installed Erlang 22. Got an error trying to install Elixir.
Installed Erlang 20. Got an error installing Elixir about being compiled in a different version of Erlang. optcode 150-something, but used optcode 168.
Installed Version 21. Same error - only have up to optcode 163, but need up to 168.
Read some github entry which suggest that an error was fixed after 21.0.
Installed 21.1. Crashed, at some make file recipe for targe erlang failed.
Installed 21.2. Crashed, makefile 64: recipe for target erlang failed.
Not sure if its relevant, but I noticed that erlang --version returns command not found: erlang.
Can anyone suggest for me a combination of elixir version and erlang version that should work together? Or help me resolve this problem another way?
I’ve been using Erlang OTP.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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.
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
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!"
First Post!- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
This seems to be quite a lot of trying. Can you please remove all of your installation attempts?
Then it’s probably easiest to switch to Arch Linux
or just use a toolset manager like
asdf-vm. It will be able to install, run and change appropriate version sets as you specify them per project.Also in the official documentation there is a compatibility matrix that tells you which version of elixir is known to work with which version of Erlang.
Just remember that the runtime version of Erlang needs to be equal to or greater than the version used for compiling.
Most Liked
ConnorRigby
alicektx
…just joined here in order to clarify a few things for future reference,
hopefully it will save others from similar headaches as per above.
Erlang Solutions’ instructions per se indeed don’t / won’t work on Mint ‘as is’. But…
that has absolutely nothing to do though whatsoever with Mint somehow having a different package base or dependencies etc.
The ‘fault’ lies in their installer’s routine, erlang-solutions_1.0_all.deb…that’s what’s to be blamed
What it does, is that it parsers /etc/issue for the identification of the numerous Ubuntu & Debian versions,
then nicely sets the repositories accordingly to the version detected.
But…by parsing the non-standard /etc/issue, which will 99% return a different id,
in any Ubuntu / Debian derivative out there…it fails on such.
A by far more proper way would be if they checked /etc/lsb-release.
Actually, even better than such, if we are to go with the freedesktop standards nowadays, /etc/os-release instead.
Although as we all understand…admittedly even then some distros would fail to comply, lol…
Hopefully Erlang Solutions will revisit their os detection routine at some point,
at least without relying entirely on /etc/issue…
For the time being, on Ubuntu derivatives, someone can ‘bypass’ the erlang-solutions_1.0_all.deb method,
by following these instructions here…
https://forums.linuxmint.com/viewtopic.php?p=1603722#p1603722
That’s for older Mint 18 (xenial). For Mint 19 (bionic), obviously the line should instead be ubuntu bionic contrib…
…bend wasn’t the first one to be hit by this, that’s what i’m trying to say
Just noticed his thread over at LM’s forums today…
where people also told him to use the erlang-solutions.deb,
apparently unaware of what goes on. Had i seen his thread earlier,
i’d have posted / replied there, but maybe that’s for the better…
Thought i’d mention the above here, so in case some other fella in the future,
from whatever other Ubuntu / Debian derivative comes asking,
can probably understand what’s going on & save his/her time…
Or so that you guys around here can guide him on what to do to easily add the repos & packages properly:
all that’s needed is to add the appropriate matching repo in sources.list
Or maybe the ES people eventually notice it, and then fine-tune / somehow tweak the routine in their ‘setup’ .deb…
peerreynders
Installing Elixir on Linux (with asdf)