[erlang-questions] Default install prefix
13 views
Skip to first unread message
Forrest Aldrich
May 25, 2012, 5:31:04 PM5/25/12
to erlang-q...@erlang.org
My configure flags are pretty straightforward:
./configure --prefix=/usr --enable-m64-build --without-javac --with-odbc=/usr
WHY does erlang insist on doing this for the installation?
/usr/lib/erlang/bin/./erl
No other program is going to find this in a reasonable $PATH setting.
The ./configure --prefix=/usr should assume /usr as the root and bin/ underneath that, just like any other program. Am I missing something here.
Forrest
./configure --prefix=/usr --enable-m64-build --without-javac --with-odbc=/usr
WHY does erlang insist on doing this for the installation?
/usr/lib/erlang/bin/./erl
No other program is going to find this in a reasonable $PATH setting.
The ./configure --prefix=/usr should assume /usr as the root and bin/ underneath that, just like any other program. Am I missing something here.
Forrest
Dmitry Kolesnikov
May 25, 2012, 5:59:01 PM5/25/12
to Forrest Aldrich, erlang-q...@erlang.org
Hello,
you should have /usr/bin and it should contains a symbolic links to ../lib/erlang/bin/*
I do not know what was the actual design decision to put binaries under ../lib/erlang/bin but I am suspecting it facilitates "release" creation. The release contains a full VM binaries and erts it is much more easy to tar gzip ../lib/erlang/bin instead of filtering /usr/bin for relevant files.
- Dmitry
> _______________________________________________
> erlang-questions mailing list
> erlang-q...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
you should have /usr/bin and it should contains a symbolic links to ../lib/erlang/bin/*
I do not know what was the actual design decision to put binaries under ../lib/erlang/bin but I am suspecting it facilitates "release" creation. The release contains a full VM binaries and erts it is much more easy to tar gzip ../lib/erlang/bin instead of filtering /usr/bin for relevant files.
- Dmitry
> erlang-questions mailing list
> erlang-q...@erlang.org
> http://erlang.org/mailman/listinfo/erlang-questions
_______________________________________________
erlang-questions mailing list
erlang-q...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions
Tim Watson
Jun 1, 2012, 4:09:19 AM6/1/12
to Forrest Aldrich, erlang-q...@erlang.org
Sounds reasonable to me. On the other hand....
cd r13src && ./configure --prefix=/opt/erlang/versions/R13B01 --etc && make && make install
cd r14src && ./configure --prefix=/opt/erlang/versions/R14B01 --etc && make && make install
...etc
ln -s /opt/erlang/versions/R14B01 /opt/erlang/current
export PATH="/opt/erlang/current/bin:$PATH"
export ERL_TOP="opt/erlang/current"
That way you can swap 'em around easily. You can also use https://github.com/spawngrid/kerl for this, or https://github.com/hyperthunk/evm (which is incredibly stupid, but therefore easy not to get confused by).
cd r13src && ./configure --prefix=/opt/erlang/versions/R13B01 --etc && make && make install
cd r14src && ./configure --prefix=/opt/erlang/versions/R14B01 --etc && make && make install
...etc
ln -s /opt/erlang/versions/R14B01 /opt/erlang/current
export PATH="/opt/erlang/current/bin:$PATH"
export ERL_TOP="opt/erlang/current"
That way you can swap 'em around easily. You can also use https://github.com/spawngrid/kerl for this, or https://github.com/hyperthunk/evm (which is incredibly stupid, but therefore easy not to get confused by).
Reply all
Reply to author
Forward
0 new messages