From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 4FA627EE42 for ; Fri, 14 Jun 2013 14:02:56 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of omeragacan@gmail.com) identity=pra; client-ip=74.125.82.42; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="omeragacan@gmail.com"; x-sender="omeragacan@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of omeragacan@gmail.com designates 74.125.82.42 as permitted sender) identity=mailfrom; client-ip=74.125.82.42; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="omeragacan@gmail.com"; x-sender="omeragacan@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wg0-f42.google.com) identity=helo; client-ip=74.125.82.42; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="omeragacan@gmail.com"; x-sender="postmaster@mail-wg0-f42.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj0DAGEFu1FKfVIqjWdsb2JhbABagzlJgjgBrTuOZn4IFg4BAQEBBwsLCRIGJIIjAQEEAUABGx0BAwELBgULAzgiAREBBQEcBogOAQMJBpx/jEuCf4ROChknDViHdAEFDI88B4NgA4kajieBKY40FimEODk X-IPAS-Result: Aj0DAGEFu1FKfVIqjWdsb2JhbABagzlJgjgBrTuOZn4IFg4BAQEBBwsLCRIGJIIjAQEEAUABGx0BAwELBgULAzgiAREBBQEcBogOAQMJBpx/jEuCf4ROChknDViHdAEFDI88B4NgA4kajieBKY40FimEODk X-IronPort-AV: E=Sophos;i="4.87,865,1363129200"; d="scan'208";a="21823358" Received: from mail-wg0-f42.google.com ([74.125.82.42]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 14 Jun 2013 14:02:56 +0200 Received: by mail-wg0-f42.google.com with SMTP id z11so1578746wgg.5 for ; Fri, 14 Jun 2013 05:02:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=LwxhPyKwsQCl83D/zbRLvhF5sc28AqYIhd3CZHlIm4I=; b=x8VK05QUZdfDCronFADayjOl6RDF4jjYsIFlDOl9UuFt1ZRrV+IAZw6dETc+EFwpEK k5qyXtlYQNlXkSo//TYYr5s44BwZSYJhHVU7RhEil8WS9JVUqbFKvyye0WqHitCmq4gT F/eYDz/8mPV3E87BgGJlcxGXiTeCG90RdQ/5GR/SkKxZjEBAZv97gv98RK5FO/TWNw2x Qp27B8YirK8+87d4K5pwU3p5MkxZxsFRgPG5BAYsDjj2nv+vRHaNvbEvQi86zedDfK/k Csp+2ia3LleJHV8yotOZfAoWh7Bdsd/V1dJ5deXZjwc7itiN+CavOc4oefhPeUqQzD5W p+dw== MIME-Version: 1.0 X-Received: by 10.180.20.46 with SMTP id k14mr1156330wie.14.1371211375719; Fri, 14 Jun 2013 05:02:55 -0700 (PDT) Received: by 10.216.172.72 with HTTP; Fri, 14 Jun 2013 05:02:55 -0700 (PDT) In-Reply-To: References: Date: Fri, 14 Jun 2013 15:02:55 +0300 Message-ID: From: =?ISO-8859-9?Q?=D6mer_Sinan_A=F0acan?= To: Dawid Toton Cc: caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-9 Content-Transfer-Encoding: quoted-printable Subject: Re: [Caml-list] Re: OCaml binary formats -- how are they linked? Thanks for your answer, > The OCaml compiler includes b.o and every other compiled OCaml module > in the executable. > wrappers.o and foo.o can end up as a part of dynamically linked > library, but you have choice. You can even call the linker directly > and play weird things with all the *.o files that C and OCaml > compilers produce. What do you mean by 'calling the linker'? Do you mean system level functions like `dload` (or it's equivalent for OCaml libraries) ? Or do you mean calling OCaml compiler's linker in compile time? Is there a program like `ldd` that shows dynamically linked OCaml libraries of a OCaml program? Where can I learn more about OCaml binary file formats like .cma, .cmx ? I couldn't find a related section in language manual. --- =D6mer Sinan A=F0acan http://osa1.net