Erlang/OTP系统文档：5.8.4版本安装教程

需积分: 9 58 浏览量更新于2024-07-23 收藏 960KB PDF 举报

Erlang/OTP系统文档是一份版权为1997年至2011年艾瑞克森公司的宝贵资源，包含了Erlang/OTP（Object-Oriented Programming Toolset）系统的详细介绍和安装指南。该版本为5.8.4，发布日期为2011年5月24日，遵循Erlang公共许可证1.1版。这份文档对于理解和使用Erlang/OTP在Unix或Windows系统上的安装至关重要。文档的主要内容分为两部分： 1. **安装二进制发行版** - 对于Unix系统： - 提供的是一个压缩的tar文件，这是Erlang/OTP的基础安装包。 - 安装过程涉及对在线HTML文档的浏览，以获取详细的步骤指导。用户需要下载并解压文件，然后按照指示进行配置和设置，可能包括检查依赖项、环境变量配置等。 2. **用户手册** - 本部分重点介绍如何在Unix和Windows平台上安装Erlang/OTP，包括针对不同操作系统的具体步骤。对于Unix用户，可能还会涉及到使用命令行工具，如tar和shell脚本，以及适应特定Linux发行版的注意事项。值得注意的是，使用这份文档时必须遵守Erlang Public License的条款，该软件分发是以"即用即付"（AS-IS）的方式，并且不提供任何形式的保证，无论是明示的还是默示的。用户需要在获取软件的同时获得许可证副本，可以从Erlang官方网站<http://www.erlang.org/>下载。最后，文档明确指出，所有权利归艾瑞克森公司所有，再次强调了尊重知识产权和遵循许可证协议的重要性。通过阅读和遵循这份文档，开发者和系统管理员能够有效地部署和管理Erlang/OTP系统，确保其在各种环境中的稳定性和性能。由于其详尽的指导和法律要求，它不仅是技术参考材料，也是确保合规性的关键文档。

1.3 Building and Installing Erlang/OTP

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 <ReleaseDir>

$ gunzip -c otp_html_R14B03.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 <ReleaseDir>

$ gunzip -c otp_man_R14B03.tar.gz | tar xf -

Where <ReleaseDir> is

• <PrefixDir>/lib/erlang if you have installed Erlang/OTP using make install.

• $DESTDIR<PrefixDir>/lib/erlang if you have installed Erlang/OTP using make install

DESTDIR=<TmpInstallDir>.

• RELEASE_ROOT if you have installed using make release RELEASE_ROOT=<ReleaseDir>.

1.3.7 Support for SMP (Symmetric Multi Processing)

An emulator with SMP support will be built by default on most platforms if a usable POSIX thread library or native

Windows threads is found.

You can force building of an SMP emulator, by using ./configure --enable-smp-support. However, if

configure does not automatically enable SMP support, the build is very likely to fail.

Use ./configure --disable-smp-support if you for some reason do not want to have the emulator with

SMP support built.

If SMP support is enabled, support for threaded I/O will also be turned on (also in the emulator without SMP support).

The erl command will automatically start the SMP emulator if the computer has more than one logical processor.

You can force a start of the emulator with SMP support by passing -smp enable as command line arguments to

erl, and you can force a start of the emulator without SMP support by passing -smp disable.

1.3.8 GS (Graphic System)

GS now Tcl/Tk 8.4. It will be searched for when starting GS.

1.3.9 Using HiPE

HiPE supports the following system configurations:

• x86: All 32-bit and 64-bit mode processors should work.

• Linux: Fedora Core is supported. Both 32-bit and 64-bit modes are supported.

NPTL glibc is strongly preferred, or a LinuxThreads glibc configured for "floating stacks". Old non-floating

stacks glibcs have a fundamental problem that makes HiPE support and threads support mutually exclusive.

• Solaris: Solaris 10 (32-bit and 64-bit) and 9 (32-bit) are supported. The build requires a version of the GNU C

compiler (gcc) that has been configured to use the GNU assembler (gas). Sun's x86 assembler is emphatically

not supported.

• FreeBSD: FreeBSD 6.1 and 6.2 in 32-bit and 64-bit modes should work.

• MacOSX/Darwin: Darwin 9.8.0 in 32-bit mode should work.

1.3 Building and Installing Erlang/OTP

Make sure that the command hostname returns a valid fully qualified host name (this is configured in /etc/

hostconfig).

If you develop linked-in drivers (shared library) you need to link using gcc and the flags -bundle -

flat_namespace -undefined suppress. You also include -fno-common in CFLAGS when compiling.

Use .so as the library suffix.

Universal 32bit binaries can be built on an Intel Mac using the --enable-darwin-universal configure option.

There still may occur problems with certain applications using this option, but the base system should run smoothly.

When building universal binaries on a PowerPC Mac (at least on Tiger), you must point out a suitable SDK that

contains universal binaries. For instance, to build universal binaries for Tiger (10.4):

$ CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk" \

LDFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk" \

./configure --enable-darwin-universal

Also, if you run Leopard, but want to build for Tiger, you must do by setting the MACOSX_DEPLOYMENT_TARGET

environmental variable.

$ export MACOSX_DEPLOYMENT_TARGET=10.4

Experimental support for 64bit x86 darwin binaries can be enabled using the --enable-darwin-64bit configure

flag. The 64bit binaries are best built and run on Leopard, but most of the system also works on Tiger (Tiger's 64bit

libraries are, however, limited; therefore e.g. odbc, crypto, ssl etc. are not supported in Tiger). 64bit PPC binaries

are not supported and we have no plans to add such support (no machines to test on).

Universal binaries and 64bit binaries are mutually exclusive options.

1.3.11 How to Build a Debug Enabled Erlang RunTime System

After completing all the normal building steps described above a debug enabled runtime system can be built. To do

this you have to change directory to $ERL_TOP/erts/emulator.

In this directory execute:

$ make debug FLAVOR=$FLAVOR

where $FLAVOR is either plain or smp. The flavor options will produce a beam.debug and beam.smp.debug

executable respectively. The files are installed along side with the normal (opt) versions beam.smp and beam.

To start the debug enabled runtime system execute:

$ $ERL_TOP/bin/cerl -debug

The debug enabled runtime system features lock violation checking, assert checking and various sanity checks to help

a developer ensure correctness. Some of these features can be enabled on a normal beam using appropriate configure

options.

There are other types of runtime systems that can be built as well using the similar steps just described.

1.4 Cross Compiling Erlang/OTP

• Large File Support

• Other Tools

• Cross System Root Locations

• Optional Feature, and Bug Tests

• Copyright and License

• Modifying This Document

1.4.1 Introduction

This document describes how to cross compile Erlang/OTP-R14B03. Note that the support for cross compiling Erlang/

OTP should be considered as experimental. As far as we know, the R14B03 release should cross compile fine, but

since we currently have a very limited set of cross compilation environments to test with we cannot be sure. The cross

compilation support will remain in an experimental state until we get a lot more cross compilation environments to

test with.

You are advised to read the whole document before attempting to cross compile Erlang/OTP. However, before reading

this document, you should read the $ERL_TOP/INSTALL.md document which describes building and installing Erlang/

OTP in general. $ERL_TOP is the top directory in the source tree.

otp_build Versus configure/make

Building Erlang/OTP can be done either by using the $ERL_TOP/otp_build script, or by invoking $ERL_TOP/

configure and make directly. Building using otp_build is easier since it involves fewer steps, but the

otp_build build procedure is not as flexible as the configure/make build procedure. Note that otp_build

configure will produce a default configuration that differs from what configure will produce by default. For

example, currently --disable-dynamic-ssl-lib is added to the configure command line arguments unless

--enable-dynamic-ssl-lib has been explicitly passed. The binary releases that we deliver are built using

otp_build. The defaults used by otp_build configure may change at any time without prior notice.

Cross Configuration

The $ERL_TOP/xcomp/erl-xcomp.conf.template file contains all available cross configuration variables

and can be used as a template when creating a cross compilation configuration. All cross configuration

variables are also listed at the end of this document. For examples of working cross configurations see the

$ERL_TOP/xcomp/erl-xcomp-TileraMDE2.0-tilepro.conf file and the $ERL_TOP/xcomp/erl-

xcomp-x86_64-saf-linux-gnu.conf file. If the default behavior of a variable is satisfactory, the variable

does not need to be set. However, the configure script will issue a warning when a default value is used. When

a variable has been set, no warning will be issued.

A cross configuration file can be passed to otp_build configure using the --xcomp-conf command line

argument. Note that configure does not accept this command line argument. When using the configure script

directly, pass the configuration variables as arguments to configure using a <VARIABLE>=<VALUE> syntax.

Variables can also be passed as environment variables to configure. However, if you pass the configuration in the

environment, make sure to unset all of these environment variables before invoking make; otherwise, the environment

variables might set make variables in some applications, or parts of some applications, and you may end up with an

erroneously configured build.

What can be Cross Compiled?

All Erlang/OTP applications except the wx application can be cross compiled. The build of the wx driver will currently

be automatically disabled when cross compiling.

Compatibility

The build system, including cross compilation configuration variables used, may be subject to non backward

compatible changes without prior notice. Current cross build system has been tested when cross compiling some

剩余330页未读，继续阅读

ml7000

粉丝: 0
资源: 26

Erlang/OTP系统文档：5.8.4版本安装教程

React钩子实现一次性密码输入组件 otp-input-react

Python库ob-dj-otp-0.0.10安装使用指南

构建旅行计划Web应用的OTP-UI React组件库

otp-system-documentation.pdf

Erlang Run-Time System Application

the-zen-of-elixir：反映Elixir禅的顶级文章合集

Erlang OTP系统文档简介与安装指南

Erlang/OTP系统文档：版本12.1弃用功能

EM78P447S：8位 OTP-ROM 单片机技术规格

OTP-538U：热电堆传感器技术资料

最新资源