Skip to main content

Erlang on Linux: Configuration and Installation

Erlang is a fast growing language and is used in many key applications. Being concurrent and fast..it is used in many applications where multiple service are required simultaneously. 
It can be installed on linux via it package 
or 
simply from the terminal using : sudo apt-get install erlang

I did using the source file from the erlang site.
The following steps made me complete the installation:

1>download the tar file.
2> cd to the folder and unzip it.
3> go the unzipped folder.
4> Now, Erlang needs some other files to fully complete installations and generate documentations.
  So the following steps needs to be done:
  • sudo apt­-get install fop 
  • sudo apt­-get install libncurses-5­-dev
  • sudo apt­-get install openjdk­6­-jdk
  • sudo apt­-get install unixodbc-­dev
  • sudo apt­-get install g++
  • sudo apt­-get install libssl­-dev
Still, Erlang requires wx libraries so we will do the following:
  • sudo apt­-get install libwxbase2.8
  • sudo apt­-get install libwxgtk2.8­dev
  • sudo apt­-get install libqt4­opengl­dev
  • sudo apt­-get install libgtk2.0­dev
Now, we are ready to go...
  1. cd to unzipped folder.
  2. Type: ./configure
  3. Type: make
  4. Type: sudo make install
And there it will be....your Erlang ready to goo....
Test it by typing in the terminal..
erl
2+9.
It will print: 11
or 
which erl
This is supposed to give : /usr/local/bin/erl
....So happy coding...Cheers...

...If there is any problem...let me know.. lets solve it together...

Comments

Popular posts from this blog

PromptCraft Blog Series #7: Visual Prompt Design for No-Coders – Learn how to build effective AI prompt flows using visual tools in no-code platforms like Lovable, Bubble, and more

PromptCraft Series #7 – Visual Prompt Design for No-Coders ✨ PromptCraft Series #7 "Visual Prompt Design for No-Coders" 🗕️ New post every Monday 🎨 Why Visual Prompt Design Matters Prompt engineering doesn’t have to be text-only or code-heavy. Today, powerful no-code tools allow you to design, trigger, and connect prompts visually using simple blocks, fields, and flows. Drag-and-drop interfaces reduce human error Inputs can be dynamically passed to prompt templates Output logic can be reused across different use cases Non-developers can build intelligent apps visually This blog explores how to do it right — with examples, templates, and real platform walkthroughs. 🔧 Anatomy of a Visual Prompt Block Component Purpose 🔢 Input Field Captures dynamic user input (text, image, number) 🧠 Prompt Template Combines static in...

The behind-the-scenes story of how we chose our tech stack, what went wrong, and why we changed course

The Tech Stack We Chose (And Why We Switched Midway) The Tech Stack We Chose (And Why We Switched Midway) By Rexman Published: 13/06/2025 – Behind the Scenes Series #2 🧠 The Master Plan Choosing a tech stack was easy. Or so we thought. We had a Notion page comparing Postgres vs Mongo, Firebase vs Supabase, React vs Vue vs SvelteKit. We were acting like we were choosing our life partner — when really, we just needed a stack that wouldn’t break in 3 weeks. We picked: Frontend: React Native with Expo Backend: Supabase (Postgres + Auth) Storage: Supabase Storage AI integration: Claude (Anthropic) Deployment: Vercel 💥 Reality Bites Week 1 was smooth. By Week 2, cracks appeared. Supabase’s Postgres was fine… until our expensive queries choked it. React Native was okay, but we hit prop-passing hell fast. Claude integration was awesome… until we realized we needed more dynamic prompt chaining a...

PromptCraft Blog Series #6: Prompt Debugging and Optimization – Learn how to fix and improve AI prompt outputs for more accurate, helpful results.

PromptCraft Series #6 – Prompt Debugging and Optimization "As of May 2025, summarize one real, recent science discovery based on known sources. Add links if available and avoid speculation." ✨ PromptCraft Series #6 "Prompt Debugging and Optimization: Getting the Output You Want" 🗕️ New post every Monday 🔍 Why Prompts Sometimes Fail Even the best models can give you: ❌ Irrelevant answers ❌ Generic or vague responses ❌ Hallucinated facts or made-up data ❌ Wrong tone or misunderstanding of intent Often, it’s not the AI’s fault — it’s the prompt . 🔧 How to Debug a Prompt Start with these questions: Is the role or task clearly defined? Did you give examples or context? Are your constraints too loose or too strict? Did you format the output instructions properly? Then iterate your prompt, one element at...