[erlang-questions] Creating an application that is portable across versions of CentOS

[jim rosenblum]

I have a standard OTP application in which I use Rebar to generate a
release.
When I tar up the appropriate release directory, I can explode it on
another CentOS 6.2 machine, and it will run with no problems. But when I
explode it on a CentOS 5.2 machine, it will not run giving the following
output:

#bin/jc console
Exec: /root/test/jc/erts-6.2/bin/erlexec -boot
/root/test/jc/releases/1.0.0/jc -mode embedded -config
/root/test/jc/releases/1.0.0/sys.config -args_file
/root/test/jc/releases/1.0.0/vm.args -- console
Root: /root/test/jc
bin/jc: line 224: /root/test/jc/erts-6.2/bin/erlexec: cannot execute binary
file
bin/jc: line 224: /root/test/jc/erts-6.2/bin/erlexec: Success

Should this work? If so, can someone share the tricks to portability.

The version of Erlang that I build on is:
Erlang/OTP 17 [erts-6.2] [source-5c974be] [64-bit] [smp:2:2]
[async-threads:10] [hipe] [kernel-poll:false]

The erl_opts in the rebar.config does not include the atom native:
{erl_opts, [warn_missing_spec, {parse_transform, lager_transform}]}.

Any help would be much appreciated.

Jr0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141219/025a3858/attachment.htm>