[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Xavier Leroy <Xavier.Leroy@i...> |
| Subject: | Re: Stdlib doubts |
> In the stdlib directory of ocaml 2.04 , I find the result of make to be > something like what is shown below. What is the significance of > 'ocamlrun' here? > > ../boot/ocamlrun ../boot/ocamlc -g -nopervasives -c pervasives.mli > ../boot/ocamlrun ../boot/ocamlc -g -nopervasives -c pervasives.ml > ../boot/ocamlrun ../boot/ocamlc -g -c list.mli > > The problem I face is that I have a ocamlrun cross system which cannot run > on Linux. I am asking this because one can always compile using > 'ocamlc' directly ie. without using ocamlrun. Yes, but only once the system has been installed. (ocamlc is a script starting with e.g. #!/usr/local/bin/ocamlrun, so it can be run directly only after ocamlrun is installed in /usr/local/bin.) While the system is being built, it is necessary to say where ocamlrun resides. For your particular situation (cross-compiling), as I explained to you before, you want boot/ocamlrun to be the native (not cross-compiled) runtime system, and byterun/ocamlrun to be the cross-compiled, runtime system, suitably modified for your target architecture. - Xavier Leroy