From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id FAA22196; Tue, 20 Jul 2004 05:31:19 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id FAA25409 for ; Tue, 20 Jul 2004 05:31:18 +0200 (MET DST) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from mwinf0504.wanadoo.fr (smtp5.wanadoo.fr [193.252.22.26]) by nez-perce.inria.fr (8.12.10/8.12.10) with ESMTP id i6K3VHEV020086; Tue, 20 Jul 2004 05:31:17 +0200 Received: from pegasos (AStrasbourg-251-1-3-228.w82-126.abo.wanadoo.fr [82.126.193.228]) by mwinf0504.wanadoo.fr (SMTP Server) with ESMTP id CF2BC100034B; Tue, 20 Jul 2004 05:31:16 +0200 (CEST) Received: from luther by pegasos with local (Exim 4.34) id 1BmlLj-0003Xo-2q; Tue, 20 Jul 2004 05:31:27 +0200 Date: Tue, 20 Jul 2004 05:31:26 +0200 To: Xavier Leroy Cc: Sven Luther , caml-list@inria.fr, 256900@bugs.debian.org Subject: Re: [Caml-list] prelinking ocamlfind Message-ID: <20040720033126.GA11944@pegasos> References: <20040716144701.GB1905@yquem.inria.fr> <20040717150442.GA25514@pegasos> <20040719134845.GB30112@yquem.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20040719134845.GB30112@yquem.inria.fr> User-Agent: Mutt/1.5.6+20040523i From: Sven Luther X-Miltered: at nez-perce with ID 40FC9205.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 ocamlfind:01 sven:01 luther:01 sven:01 luther:01 2004:99 fork:01 initialized:01 ocamlc:01 ocamlc:01 -output-obj:01 -output-obj:01 bug:01 arrays:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk 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 :-) Hehe. > > 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. Friendly, Sven Luther ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners