Re: [Caml-list] Re: OCaml binary formats -- how are they linked?

["Ömer Sinan Ağacan" <omeragacan@gmail.com>]

Dawid, thanks for your answer. It really helped.

And now I have some more questions(that's a part of learning process, right? ;-)

> You can see what actually happens with
>
> ocamlopt -verbose -c a.ml
> ocamlopt -verbose -cc 'gcc --verbose' a.cmx

I added -verbose parameter in my Makefile, and output was interesting,
it called gcc! At first I thought it's called just for linking
purposes, but later I realized there is also a C file passed to gcc.

It first passed output parameter (`-o executableName`), later some -L
parameters. And after that it passed the file `/tmp/camlprimcb16b7.c`.
What is that file? I couldn't read it because it was deleted after
compilation.

Later some parameters are passed for statically linking(-ldl, -lm,
-lpthread, -lcamlrun etc.).


> strace -e trace=open ./myexecutable

This is so great .. A format-independent way to see dynamically linked
libraries. Thanks for the tip! (btw, is there a different name given
to the process of dynamically loading and linking libraries with
`dload` like system calls? is it also called `dynamically linked`?)


> Bytecode is compiled to a files with #! prefix.

Interesting, I just tried reading an OCaml executable created with
ocamlc, and it had a ELF header. Am I compiling to my program to
native by mistake? I'm not calling ocamlopt, only ocamlc.

Thanks again,


---
Ömer Sinan Ağacan
http://osa1.net