From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by yquem.inria.fr (Postfix) with ESMTP id BCEB6BB81 for ; Mon, 26 Sep 2005 05:09:07 +0200 (CEST) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j8Q396JE023239 for ; Mon, 26 Sep 2005 05:09:07 +0200 Received: by xproxy.gmail.com with SMTP id t11so437795wxc for ; Sun, 25 Sep 2005 20:09:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=DR6VIUxiXlmJM+/YVnDtLLKvIY1CzenUlrSJEM3RbWzGn5FbpgQz+UDaFS+8QsHJpReBnLSkZSzLm+h2PEAh5BUo9Ry7+aGYZqS56rF+PM31f48GffLdz4cLDX+SStla/r4wsp0FCRtYT73uKQmkTA6fYpr1I/SL3/IfnLEVp10= Received: by 10.70.91.7 with SMTP id o7mr2015091wxb; Sun, 25 Sep 2005 20:09:06 -0700 (PDT) Received: by 10.70.73.9 with HTTP; Sun, 25 Sep 2005 20:09:06 -0700 (PDT) Message-ID: Date: Mon, 26 Sep 2005 15:09:06 +1200 From: Jonathan Roewen Reply-To: Jonathan Roewen To: caml-list@yquem.inria.fr Subject: [Caml-list] Dynamic linking MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Miltered: at nez-perce with ID 43376653.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; caml-list:01 ocaml:01 runtime:01 ocaml:01 cmi:01 cmx:01 cmi:01 runtime:01 dynlink:01 asmdynlink:01 bytecode:01 functions:01 kernel:01 kernel:01 native:02 X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled version=3.0.3 Hi, We're trying to figure out how to provide some sort of dynamic linker for DST to load ocaml native code at runtime on an ocaml native code kernel. Is there any document that details the format of .cmi/.cmx files; also, are these (esp .cmi) able to provide the necessary details on the symbols in the kernel for building a dynamic linker that can resolve symbols to kernel functions in ocaml code loaded at runtime? I know Dynlink module doesn't work with native code, and if I'm correct, the unsupported Asmdynlink module provided a runtime environment for bytecode ocaml code in native code programs right? Which is not what we'd be looking for. Sorry if my questions come across a bit weird: it's not an easy subject for me to think about ;-) Kindest Regards, Jonathan