I have taken the linux download (x86) from
installed it, configured it and confirmed it is good and in working order. Then I try to rebuild from source, copy one beam file into place (just to confirm I can build from source) and it blows up at me.
My steps:
install
run ejabberdctl live and confirm functions correctly
I then shut everything down
I download the sources from the same process one link
run configure
run make
this is all on the same linux machine
I have no errors and no warnings from the build, with no code changes from the source distribution I downloaded
I then copy ejabberd_commands.beam to
/lib/ejabberd-2.1.11/ebin/
-- essentially I'm trying to confirm I have the right source and can build from source so that I can make changes to ejabberd_commands.erl
Running ejabberdctl live results in
Eshell V5.8.5 (abort with ^G)
(ejabberd@centora)1>
=ERROR REPORT==== 13-Jul-2012::07:54:15 ===
beam/beam_load.c(1365): Error loading module ejabberd_commands:
use of opcode 153; this emulator supports only up to 152
=ERROR REPORT==== 13-Jul-2012::07:54:15 ===
Loading of /opt/ecs/ejabberd-2.1.11/lib/ejabberd-2.1.11/ebin/ejabberd_commands.beam failed: badfile
=INFO REPORT==== 13-Jul-2012::07:54:15 ===
application: ejabberd
exited: {bad_return,
{{ejabberd_app,start,[normal,[]]},
{'EXIT',
{undef,
[{ejabberd_commands,init,[]},
{ejabberd_app,start,2},
{application_master,start_it_old,4}]}}}}
type: temporary
q().
ok
So, what am I doing to mess this up? Is there a command I can run to get the same type of tar.gz file that is spit out on the process one download page? I have tried looking at make install and I do not see where (if I was to run it) a tar.gz file would be created similar to what is on the download link. Are the distribution zip files being built by hand?
Thanks,
Zach Calvert
Nevermind, I see that I'm
Nevermind, I see that I'm compiling with 5.9.1 erlang vs running on ejd's 5.8.5