Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Erlang C C++ Makefile Java HTML Other

This branch is 35 commits ahead, 4581 commits behind maint

Failed to load latest commit information.
HOWTO Refuse to build SMP runtime by default without native atomics
bin The R13B03 release.
bootstrap Merge branch 'nox/match-context-return' into pu
erts Merge branch 'hm/reltool_script' into pu
lib Merge branch 'nox/match-context-return' into pu
make Add 'frmptr' emulator type
plt The R13B03 release.
system Fix Nif doc typos
xcomp Add an xcomp file for Blue Gene/Q
.gitattributes Stop including in .gitignore files in the source tar files
.gitignore Properly ignore os_mon and otp_mibs generated includes
.mailmap Add .mailmap file
AUTHORS The R13B03 release.
EPLICENCE The R13B03 release. Publish reltool script readme: changed information about pull requests
TAR.include Move README and INSTALL to HOWTO folder
aclocal.m4 Fix configure detection of ethread native atomics on powerpc Refuse to build SMP runtime by default without native atomics OTP-8323 Cross compilation improvements and other build system
otp_build If GCC is used, treat -Wreturn-type as error
prebuild.delete Regenerate bootstrap/{erl,erlc} when switching target
prebuild.skip OTP-8323 Cross compilation improvements and other build system


Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecom, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.

OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.

More information can be found at

Building and Installing

Information on building and installing Erlang/OTP can be found in the $ERL_TOP/HOWTO/ document.

Contributing to Erlang/OTP

Here are the instructions for submitting patches.

In short:

  • We prefer to receive proposed updates via email on the erlang-patches mailing list or through a pull request.

  • Pull requests will be handled once everyday and there will be essential testing before we will take a decision on the outcome of the request. If the essential testings fails, the pull request will be closed and you will have to fix the problem and submit another pull request when this is done.

  • We merge all proposed updates to the pu (proposed updates) branch, typically within one working day.

  • At least once a day, the contents of the pu branch will be built on several platforms (Linux, Solaris, Mac OS X, Windows, and so on) and automatic test suites will be run. We will email you if any problems are found.

  • If a proposed change builds and passes the tests, it will be reviewed by one or more members of the Erlang/OTP team at Ericsson. The reviewer may suggest improvements that are needed before the change can be accepted and merged.

  • Once or twice a week, a status email called "What's cooking in Erlang/OTP" will be sent to the erlang-patches mailing list.

Copyright and License


Copyright Ericsson AB 2010-2012. All Rights Reserved.

The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at

Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.


Something went wrong with that request. Please try again.