[erlang-questions] Keep multiple erlang releases in the same mechine
Sun Dec 17 17:26:45 CET 2006
I believe it looks under $INSTALL_PATH/lib/erlang/man, where
$INSTALL_PATH is /usr/local or /opt/erlang/current in your case.
Note that man pages are not included in the tarball of the source code,
you need to download/untar that separately.
Sanjaya Vitharana wrote:
> Hi Serge,
> Accept my thanks.
> All works fine. except erl -man <manual name>. do you know how to fix it to
> work with multiple releases?
> I mean if shifted to the diffrent release using "ln -s /opt/erlang/<release>
> /opt/erlang/current". man pages related to that release should display with
> erl -man <manual name>. I have no idea about where erl -man looks for man
> Any idea ?
> Sanjaya Vitharana
> ----- Original Message -----
> From: "Serge Aleynikov" <>
> To: "Sanjaya Vitharana" <>
> Cc: <>
> Sent: Friday, 15 December 2006 10:49 pm
> Subject: Re: [erlang-questions] Keep multiple erlang releases in the same
>> Sanjaya Vitharana wrote:
>>>> and also create a link to the most recent release:
>>>> ln -s /opt/erlang/R11B-2 /opt/erlang/current
>>> Thanks Serge ...... this seems good for me too. But what about the
>> What about it? You need to have ERL_TOP explicitly set only when you
>> are doing a custom invocation of "make" in some leaf of the OTP tree
>> during a build process. Once you have OTP installed (such as using the
>> "config --prefix="..." option, "make" and "make install"), you don't
>> need ERL_TOP set.
>>>> Then the programs such as /usr/local/bin/erl can be pointed to:
>>> means .... all the ERL_BASE_PUB_FILES (in Makefile) should repoint to
>>> /opt/erlang/current/bin/<program file>. Is it ?
>> Yes. Or else use the PATH environment setting as Dominic suggested.
>> Serge Aleynikov
>> Routing R&D, IDT Telecom
>> Tel: +1 (973) 438-3436
>> Fax: +1 (973) 438-1464
More information about the erlang-questions