and with
which ocamlrun
you get the info, which one is used.
Ciao,
Oliver
On Sun, Dec 18, 2011 at 01:30:25PM +0900, Jacques Garrigue wrote:
This basically means that you have 2 ocamlrun on this machine.
./prog calls ocamlrun with a fixed path, but the 1st ocamlrun is your
path is an
Hello.
Do head -1 prog to see the right ocamlrun.
Thank you, this really helped, but in the other way.
I've found that this executable has ELF format.
So, this is a -custom linked bytecode executable.
But I can't find anywhere in the documentation
any information about whether can I /
Am Sonntag, den 18.12.2011, 17:39 +0200 schrieb Dmitry Grebeniuk:
Hello.
Do head -1 prog to see the right ocamlrun.
Thank you, this really helped, but in the other way.
I've found that this executable has ELF format.
So, this is a -custom linked bytecode executable.
But I can't find
Hello.
So, this is a -custom linked bytecode executable.
Thanks for clarifications about -custom and dynamic loading.
ocamlc -o myrun -make-runtime unix.cma
Then ./myrun prog should work (provided that Unix is the only missing
lib).
Yes, it works (fails on the next required library).
Am Sonntag, den 18.12.2011, 18:40 +0200 schrieb Dmitry Grebeniuk:
Hello.
So, this is a -custom linked bytecode executable.
Thanks for clarifications about -custom and dynamic loading.
ocamlc -o myrun -make-runtime unix.cma
Then ./myrun prog should work (provided that Unix is the
Hello.
The OCaml manual states that executing bytecode program
with ./prog and ocamlrun ./prog should give the same result
(in simple case, without options and environment modifications).
However in my case the result is different: ./prog executes
well, but ocamlrun ./prog gives
Fatal error:
This basically means that you have 2 ocamlrun on this machine.
./prog calls ocamlrun with a fixed path, but the 1st ocamlrun is your
path is an incompatible one.
Do head -1 prog to see the right ocamlrun.
Jacques Garrigue
-
From: Dmitry Grebeniuk gds...@gmail.com
Hello.
The OCaml manual
