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 mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by sympa.inria.fr (Postfix) with ESMTPS id 9A9C47ED7A for ; Thu, 20 Sep 2012 21:50:19 +0200 (CEST) Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of Zhi.Han@mathworks.com) identity=pra; client-ip=144.212.95.218; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="Zhi.Han@mathworks.com"; x-sender="Zhi.Han@mathworks.com"; x-conformance=sidf_compatible Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of Zhi.Han@mathworks.com) identity=mailfrom; client-ip=144.212.95.218; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="Zhi.Han@mathworks.com"; x-sender="Zhi.Han@mathworks.com"; x-conformance=sidf_compatible Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@smtp2.mathworks.com) identity=helo; client-ip=144.212.95.218; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="Zhi.Han@mathworks.com"; x-sender="postmaster@smtp2.mathworks.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AskCANJxW1CQ1F/ae2dsb2JhbABFgksjuj8jAQELCwoIFAUigiIBBC0mOAEMHlYXAQ4BBBuHewGYaaFDkH5gA6hsghc X-IronPort-AV: E=Sophos;i="4.80,455,1344204000"; d="scan'208,217";a="156442125" Received: from smtp2.mathworks.com ([144.212.95.218]) by mail4-smtp-sop.national.inria.fr with ESMTP; 20 Sep 2012 21:50:18 +0200 Received: from mail-vif.mathworks.com (newscl02ah.mathworks.com [144.212.95.122]) by smtp2.mathworks.com (8.13.8/8.12.11) with ESMTP id q8KJoGLY009727 for ; Thu, 20 Sep 2012 15:50:17 -0400 (EDT) Received: from EXHUB-01-AH.ad.mathworks.com (exhub-01-ah.mathworks.com [172.31.22.59]) by mail-vif.mathworks.com (8.13.8/8.13.8) with ESMTP id q8KJoGVo006065 for ; Thu, 20 Sep 2012 15:50:16 -0400 (EDT) Received: from exmb-01-ah.ad.mathworks.com ([fe80::3987:755c:46c7:f770]) by EXHUB-01-AH.ad.mathworks.com ([::1]) with mapi id 14.02.0283.003; Thu, 20 Sep 2012 15:50:16 -0400 From: Zhi Han To: "caml-list@inria.fr" Thread-Topic: Build OCaml on linux Thread-Index: Ac2XaSaEhpHlHaoKTmCUTyXroToZlg== Date: Thu, 20 Sep 2012 19:50:15 +0000 Message-ID: <04644211E51C7E40BF64101089F97E4D0A7AE3DD@exmb-01-ah.ad.mathworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.28.154.42] Content-Type: multipart/alternative; boundary="_000_04644211E51C7E40BF64101089F97E4D0A7AE3DDexmb01ahadmathw_" MIME-Version: 1.0 X-Validation-by: zhi.han@mathworks.com Subject: [Caml-list] Build OCaml on linux --_000_04644211E51C7E40BF64101089F97E4D0A7AE3DDexmb01ahadmathw_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I found that the OCaml executable "bin/ocaml" is built by default as an byt= ecode on Linux, i.e., it requires 'bin/ocamlrun" to run it. This has caused= some issues in our group because our build process copies the executables = from place to place. When the files are moved, the old location of the file= is left in the first line of the bytecode file. However, same issues does not exists on Windows build. The files are built = as executables and we can move these files around and still be able to exec= ute them. I am wondering what are the switches that makes the Windows build= work. Can somebody help me with that? Thanks, Zhi --_000_04644211E51C7E40BF64101089F97E4D0A7AE3DDexmb01ahadmathw_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I found that the OCaml executable “bin/ocaml&#= 8221; is built by default as an bytecode on Linux, i.e., it requires ‘= ;bin/ocamlrun” to run it. This has caused some issues in our group be= cause our build process copies the executables from place to place. When the files are moved, the old location of the file is left i= n the first line of the bytecode file.

 

However, same issues does not exists on Windows buil= d. The files are built as executables and we can move these files around an= d still be able to execute them. I am wondering what are the switches that = makes the Windows build work. Can somebody help me with that? Thanks,

 

Zhi

--_000_04644211E51C7E40BF64101089F97E4D0A7AE3DDexmb01ahadmathw_--