Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] prelinking ocamlfind
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Sven Luther <sven.luther@w...>
Subject: Re: [Caml-list] prelinking ocamlfind
On Mon, Jul 19, 2004 at 03:48:46PM +0200, Xavier Leroy wrote:
> > Xavier, i have been told that this probably happens because we use a elf
> > section that is normally strippable.
> It's even worse than that, but I won't get into details :-)


> > It could be solved by using a
> > special elf section specialized to our need (maybe one named bytecode or
> > something), then at least strip and possibly the prelink stuff, would
> > not remove it as it does not.
> Yes, but:
> - This solution is not portable to non-ELF platforms (e.g. MS Windows),
>   thus forcing an unpleasant fork in the code.
> - The ELF format is very complex.  There are libraries that facilitate
>   manipulations of ELF files (e.g. libelf), but these are not
>   universally available and severely under-documented.
> Rather than muck with ELF, a simpler solution would be to embed the
> bytecode executable as initialized C arrays in the executable
> generated by ocamlc -custom.  That's what ocamlc -output-obj does, and
> I believe it shouldn't be too hard to adapt the existing -output-obj
> code to the -custom case.

Mmm. Ok, it will be ocaml 3.09 stuff though.

CCing this to the relevant debian bug report. 


Sven Luther

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: