<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 25/05/2012 22:31, Forrest Aldrich wrote:
<blockquote cite="mid:4FBFFA18.4080700@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
My configure flags are pretty straightforward:<br>
<br>
./configure --prefix=/usr --enable-m64-build --without-javac
--with-odbc=/usr<br>
<br>
WHY does erlang insist on doing this for the installation?<br>
<br>
/usr/lib/erlang/bin/./erl<br>
<br>
No other program is going to find this in a reasonable $PATH
setting.<br>
<br>
The ./configure --prefix=/usr should assume /usr as the root and
bin/ underneath that, just like any other program. Am I missing
something here.<br>
</blockquote>
Sounds reasonable to me. On the other hand....<br>
<br>
cd r13src && ./configure
--prefix=/opt/erlang/versions/R13B01 --etc && make
&& make install<br>
cd r14src && ./configure
--prefix=/opt/erlang/versions/R14B01 --etc && make
&& make install<br>
...etc<br>
<br>
ln -s /opt/erlang/versions/R14B01 /opt/erlang/current<br>
export PATH="/opt/erlang/current/bin:$PATH"<br>
export ERL_TOP="opt/erlang/current"<br>
<br>
That way you can swap 'em around easily. You can also use
<a class="moz-txt-link-freetext" href="https://github.com/spawngrid/kerl">https://github.com/spawngrid/kerl</a> for this, or
<a class="moz-txt-link-freetext" href="https://github.com/hyperthunk/evm">https://github.com/hyperthunk/evm</a> (which is incredibly stupid, but
therefore easy not to get confused by).<br>
<br>
</body>
</html>