Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

All of the public Erlang/OTP source releases (since R6B-0 in 1999) in convenient git form

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 bootstrap
Octocat-spinner-32 erts
Octocat-spinner-32 lib
Octocat-spinner-32 make
Octocat-spinner-32 AUTHORS
Octocat-spinner-32 EPLICENCE
Octocat-spinner-32 Makefile.in
Octocat-spinner-32 README
Octocat-spinner-32 configure
Octocat-spinner-32 configure.in
README
===========================================================================
                          OpenSource Erlang/OTP 
===========================================================================


Please read the whole file before attempting to build and install Erlang.
You can find more information about OpenSource Erlang at

  http://www.erlang.org/


Portability
-----------

Erlang/OTP should be possible to build from source on any Unix
system. There is currently no source build for Windows but you can
download the binary release from http://www.erlang.org/.

At Ericsson we have a "Daily Build and Test" that runs on:
 
    Operating system      Version
    -----------------------------------------------------------
    Solaris/Sparc         2.5.1
    Solaris/Sparc         2.8
    Solaris/x86           2.5.1    (1)
    Linux/RedHat x86      5.2
    Linux/RedHat x86      6.2
    Linux/RedHat x86      7.1      (2)
    Linux/Debian x86      2.2
    Linux/Debian PowerPC  2.2      (3)
    FreeBSD x86           4.1.1
    Darwin/OS X PowerPC   10.0.3   (4)

(1) Not tested for a couple of months.
(2) This distribution was updated to kernel 2.4.5, glibc 2.2.2 and
    jdk 1.3.1_01.
(3) Runs on an Apple iMac, not tested for a couple of months.
(4) Runs on an Apple iMac, not tested for a couple of weeks.
    This port is not completed, see notes below.


Required utilities
------------------

These are the tools you will need in order to unpack and build Erlang/OTP.

  Unpacking
  ---------

  GNU unzip, or a modern uncompress.

  A TAR program that understand the GNU TAR format for long
  filenames (such as e.g. GNU TAR).
  

  Compiling
  ---------

  GNU make

  GNU C compiler

  Perl 5

  nawk                  Optional but needed to convert V2 SNMP MIBS to
                        V1 MIBS. "gawk" will do but you have to create
                        a link from "nawk" to the "gawk" executable.  

  openSSL/ssleay        Optional but needed for building the Erlang/OTP
                        applications 'ssl' and 'crypto'. You need the
                        "development package" of SSL, i.e. including
                        the header files.

  Sun Java jdk-1.2.2    Optional but needed for building the Erlang/OTP
                        application 'jinterface' and parts of 'ic'
                        and 'orber'.

  X Windows             Optional but development headers and libraries
                        are needed to build Erlang/OTP application 'gs'
			on Unix/Linux.

  sed			There seem to be some problems with some of the
			'sed' version at Solaris. Make sure "/bin/sed"
			or "/usr/bin/sed" is used on the Solaris platform.

  m4                    GNU m4 is needed for building HiPE.

  Installing
  ----------

  An install program that can take multiple file names


How to build and install Erlang/OTP
-----------------------------------

Start by unpacking the Erlang/OTP distribution file with your
GNU compatible TAR

  1)    gunzip -c otp_src_R8B-0.tar.gz | tar xf -
  1)    zcat otp_src_R8B-0.tar.gz | tar xf -

Now cd into base directory

  2)    cd otp_src_R8B-0

Run the following commands

  3)    ./configure  [ options ]

If you upgraded the source with the patch you may need to clean up
from previous builds before the new build. Do a "make clean", see
"Caveats" below.

  4)    make
  5)    make install

Let's go through them in some detail:

    Step 3 runs a configuration script created by the GNU autoconf
utility, which checks for system specific features and the creates a
number of makefiles. The configure script allows you to customize a
number of parameters, type "./configure --help" for details. One of
the things you can specify is where Erlang/OTP should be installed, by
default Erlang/OTP will install in /usr/local/{bin,lib/erlang,man/man1},
to keep the same structure but install in a different place, let's
call it <Dir>, than /usr/local use the --prefix argument. Like so:
"./configure --prefix=<Dir>". This step will also configure any
additional libraries unpacked in step 3 (if you didn't add any of the
extra libraries configure will issue a warning saying that there is no
configuration information in lib, this warning can safely be ignored).

You can also specify where the openSSL/ssleay include and library
files are located or disable the use of SSL.

Other options are:

	--enable-hipe   	Enable HiPE (High-Performance Erlang).
				Only for Ultra Sparc and x86-based machines
				running Linux or Solaris/x86.
	--enable-threads	Enable threaded I/O support in
				the Erlang emulator.
	--enable-unified-heap	Experimental version of Erlang with
				a shared heap for all processes, which
				speeds up message passing.
				DOES NOT WORK WITH HiPE.

    Step 4 first builds the Erlang emulator, this will take
approximately five minutes on a reasonably fast machine. It then
proceeds to build the Erlang/OTP libraries in the "lib" subdirectory
using the built emulator and the bootstrap libraries provided in the
"bootstrap" subdirectory.  Compiling everything can take quite a long
time, expect half an hour up to a couple of hours. After step 4 is
completed you should have a working Erlang/OTP system which you can
try by typing "bin/erl". This should start up Erlang/OTP and give you
a prompt.

    Step 5 is optional. It installs Erlang/OTP (if you change your
mind about where you wish to install you can rerun step 3, without
having to do step 4 again).

If you or your system has special requirements please read the
Makefile for additional configuration information.


How to install the Erlang/OTP documentation
-------------------------------------------

For some graphical tools to find the on-line help you have to install
the HTML documentation on top of the installed OTP applications, i.e.

        cd <PrefixDir>/lib/erlang
        gunzip -c otp_doc_html_R8B-0.tar.gz | tar xf -

For "erl -man <page>" to work the Unix manual pages have to be
installed in the same way, i.e.

        cd <PrefixDir>/lib/erlang
        gunzip -c otp_doc_man_R8B-0.tar.gz | tar xf -


Using HiPE
----------

If you enabled HiPE when building (as described above),
compile an module into native code like this from the
Erlang shell:

	c(Module, native).

or

	c(Module, [native|OtherOptions]).

Using the erlc program, write like this:

	erlc +native Module.erl

The native code will be placed into the beam file and automatically
loaded when the beam file is loaded.

To add hipe options, write like this from the Erlang shell:

	c(Module, [native,{hipe,HipeOptions}|MoreOptions]).

Use

	hipe:help_options().

to print out the available options.


Darwin/OS X
-----------

This is a new port that isn't complete. The main test suites are
successful but there are more work to be done.

Use the "gnutar" command to unpack the sources.

The 'mnesia_session' application currenctly does not build on Darwin.
After "configure" but before "make" do

        touch lib/mnesia_session/SKIP

The 'orber' Erlang/OTP application will not be build because of a bug
in the configure script.

Erlang/OTP will read the network configuration files in "/etc" at
startup.  In Darwin these are normally not used by the operating
system. The easiest way to solve this is to make Erlang/OTP avoid this
is to put the line (including the ending '.')

  {lookup,["native"]}.

into the file "$HOME/.inetrc".

Make sure that the command "hostname" return a valid fully qualified
host name (this is configured in "/etc/hostconfig").


Caveats
-------

There are currently incorrect dependencies in the Makefiles, which
means that if you modify any source code the system might not build
properly. Also "make clean" does not clean out everything that should
be cleaned.


Make and the variable "ERL_TOP"
-------------------------------

All the makefiles in the entire directory tree use the environment
variable ERL_TOP to find the absolute path of the installation. The
configure script will figure this out and set it in the top level
Makefile (which, when building, it will pass on). However when
developing it is sometimes convenient to be able to run make in a
subdirectory. In order to do this you need to set the ERL_TOP variable
before you run make.

For example, assume your GNU make program is called "make" and you
wish to rebuild the Erlang/OTP part of stdlib, then you could do:

  cd lib/stdlib/src ; env ERL_TOP=<Dir> make

Where <Dir> would be what you find ERL_TOP is set to in the top level
Makefile.


More Information
----------------

More information can be found on http://www.erlang.org/

For commercial inquires (printed documentation, support et.c.) please
visit http://www.erlang.se/
Something went wrong with that request. Please try again.