<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Thomas,<br>
<br>
I believe we originally did what you are describing. Here are the
steps we took:<br>
<ol>
<li>Download src into new directory</li>
<li>./configure</li>
<li>make (OTP directory)<br>
</li>
<li>bring down our server</li>
<li>make install (OTP directory)<br>
<br>
</li>
<li>make clean (our source)</li>
<li>make</li>
<li>run server</li>
</ol>
Cheers,<br>
Bryan<br>
<br>
On 10/30/11 12:51 AM, Thomas Lindgren wrote:
<blockquote
cite="mid:1319961108.25627.YahooMailNeo@web111404.mail.gq1.yahoo.com"
type="cite">
<pre wrap="">Bryan,
Try recompiling your source with the R14B04 compiler (or in general, whatever you're targeting). That's the only solution to this I know, though I had this problem some time ago. Maybe there are better ways now.
Here's a question for OTP: shouldn't these sorts of VM-level versioning issues be detected and reported more straightforwardly? I'd prefer a root cause + what to do.
Something like, "foo.beam was compiled for vm-isa-10.0 but VM requires incompatible vm-isa-14.4. To fix this, recompile from source."
Perhaps even better: rewrite the beam files to the new instruction set en masse and/or individually at load time.
Best,
Thomas
</pre>
<blockquote type="cite">
<pre wrap="">________________________________
From: Bryan Hughes <a class="moz-txt-link-rfc2396E" href="mailto:bryan@wobblesoft.com"><bryan@wobblesoft.com></a>
To: Erlang <a class="moz-txt-link-rfc2396E" href="mailto:erlang-questions@erlang.org"><erlang-questions@erlang.org></a>
Sent: Sunday, October 30, 2011 5:10 AM
Subject: [erlang-questions] use of opcode 153; this emulator supports only up to 152 after upgrading to R140B4
Hi,
We attempted to upgrade our production server to R140B4 which we built from source on the server but had to bad out due to a serious failure. The server is running CentOS with a kernel version 2.6.18-238.12.1.el5. We did a basic .configure/make/make install like we have done every time in the past, but this time, when we tried to bring the application up, we got the following error condition:
20:55:02.946 [error] web request failed", method: 'GET', path: "ping", type: error, what: undef, trace: [{httpd_util,'rfc1123_date',[]},{mochiweb_request,server_headers,1},{mochiweb_request,start_response,2},{mochiweb_request,respond,2},{herd_web,loop,2},{mochiweb_http,headers,5},{proc_lib,init_p_do_apply,3}], request: {mochiweb_request,#Port<0.6428>,'GET',"/ping",{1,1},{12,{"host",{'Host',"herdmobile.dyndns.org:8080"},{"accept-encoding",{'Accept-Encoding',"gzip"},{"accept-charset",{'Accept-Charset',"utf-8, iso-8859-1, utf-16,
</pre>
</blockquote>
<pre wrap=""> *;q=0.7"},{"accept",{'Accept',"application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5"},nil,nil},nil},{"accept-language",{'Accept-Language',"en-US"},nil,{"connection",{'Connection',"keep-alive"},{"bandwidth",{"Bandwidth","3100000"},nil,nil},nil}}},{"x-wap-profile",{"X-Wap-Profile",<a class="moz-txt-link-rfc2396E" href="http://device.sprintpcs.com/HTC/APA9292KT/4536511.rdf">"http://device.sprintpcs.com/HTC/APA9292KT/4536511.rdf"</a>},{"x-network-type",{"X-Network-Type","EVDO"},{"referer",{'Referer',<a class="moz-txt-link-rfc2396E" href="http://herdmobile.dyndns.org:8080/ping">"http://herdmobile.dyndns.org:8080/ping"</a>},{"keep-alive",{'Keep-Alive',"115"},nil,nil},{"user-agent",{'User-Agent',"Mozilla/5.0 (Linux; U; Android 2.3.3; en-us; Sprint APA9292KT Build/GRI40) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1"},nil,nil}},nil},nil}}}}
</pre>
<blockquote type="cite">
<pre wrap="">
20:55:02.960 [error] Loading of /usr/local/lib/erlang/lib/inets-5.8/ebin/httpd_util.beam failed: badfile
20:55:02.970 [error] CRASH REPORT Process <0.138.0> with 0 neighbours crashed with reason: undef
20:55:02.982 [error] beam/beam_load.c(1365): Error loading module httpd_util:^M
use of opcode 153; this emulator supports only up to 152^M
Any help would be appreciated, we need to upgrade as we are suffering the SSL cache delete bug (<a class="moz-txt-link-freetext" href="http://erlang.org/pipermail/erlang-bugs/2011-June/002484.html">http://erlang.org/pipermail/erlang-bugs/2011-June/002484.html</a>) that the readme for R140B4 says has been fixed.
Many thanks,
Bryan
_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
</blockquote>
</body>
</html>