From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <krismicinski@gmail.com>
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 1D8477ED7A
	for <caml-list@sympa.inria.fr>; Sat, 22 Sep 2012 21:52:14 +0200 (CEST)
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  krismicinski@gmail.com) identity=pra;
  client-ip=209.85.212.54;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="krismicinski@gmail.com";
  x-sender="krismicinski@gmail.com";
  x-conformance=sidf_compatible
Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of
  krismicinski@gmail.com designates 209.85.212.54 as permitted
  sender) identity=mailfrom; client-ip=209.85.212.54;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="krismicinski@gmail.com";
  x-sender="krismicinski@gmail.com";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@mail-vb0-f54.google.com) identity=helo;
  client-ip=209.85.212.54;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="krismicinski@gmail.com";
  x-sender="postmaster@mail-vb0-f54.google.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjIBACEWXlDRVdQ2kGdsb2JhbABFviUIIwEBAQEJCQ0HFAQjgiABAQEEEgIsARsdAQMMBgULDS4iAREBBQEOAQ0GEyKHUAEDDwuZfQkDjCaCdYQ/ChknDVmIdAEFDIsQhioDlWWBFY0vFimEIw
X-IronPort-AV: E=Sophos;i="4.80,468,1344204000"; 
   d="scan'208,223";a="156611737"
Received: from mail-vb0-f54.google.com ([209.85.212.54])
  by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 22 Sep 2012 21:52:13 +0200
Received: by vbmv11 with SMTP id v11so8413102vbm.27
        for <caml-list@inria.fr>; Sat, 22 Sep 2012 12:52:12 -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=5ahAdJkK46t4KulW5Z677/Hzeqd8U1I6yBS63IqDJwE=;
        b=T6DCS+r1kkkWeF9o04wIEZEV4GP9Ux6j6CMfsfckYVkDHikShYbOMX9BAj0FrLgz+1
         KVePAiq+M48ajP4p6fV/lGIEpQ2ppDSRsTfnw1HOvnAyz9ne7wreGriQVSVGX9lv2oCF
         TugC7bKJFZubNsWEbYUPEO+3LaqC0b3t0Fo+G4EGnVNdLPOxkaUFXse4Gcar8H9rkOpT
         0i7enk+V4vtSod6fgAbUI8JL2wUQM6Pyfm82UwTfxs05xYEodDEqhRHY7NKQ6HIRmvuS
         fi7PHEKRZtAHlq441EO4n712oj35K8Wxx/L84aDu5RPNWqAMcO7wsEH2iJPKzSzvHwtX
         yWNw==
MIME-Version: 1.0
Received: by 10.58.4.131 with SMTP id k3mr5055850vek.54.1348343531869; Sat, 22
 Sep 2012 12:52:11 -0700 (PDT)
Received: by 10.58.95.104 with HTTP; Sat, 22 Sep 2012 12:52:11 -0700 (PDT)
In-Reply-To: <04644211E51C7E40BF64101089F97E4D0A7AE3DD@exmb-01-ah.ad.mathworks.com>
References: <04644211E51C7E40BF64101089F97E4D0A7AE3DD@exmb-01-ah.ad.mathworks.com>
Date: Sat, 22 Sep 2012 15:52:11 -0400
Message-ID: <CAF1Sy-E4FKsDF_gHL3He-k+9WkW0mt1Cd_K1AFYGxNNQc_herw@mail.gmail.com>
From: Kristopher Micinski <krismicinski@gmail.com>
To: Zhi Han <Zhi.Han@mathworks.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Caml-list] Build OCaml on linux

=46rom the INSTALL notes
(http://caml.inria.fr/pub/distrib/ocaml-3.12/notes/INSTALL) ...

4- If your platform is supported by the native-code compiler (as
reported during the autoconfiguration), you can now build the
native-code compiler. From the top directory, do:

        make opt
or:
        make opt > log.opt 2>&1     # in sh
        make opt >& log.opt         # in csh

Is that the sort of thing for which you're looking?

kris


On Thu, Sep 20, 2012 at 3:50 PM, Zhi Han <Zhi.Han@mathworks.com> wrote:
> Hi,
>
>
>
> I found that the OCaml executable =93bin/ocaml=94 is built by default as =
an
> bytecode on Linux, i.e., it requires =91bin/ocamlrun=94 to run it. This h=
as
> caused some issues in our group because our build process copies the
> executables from place to place. When the files are moved, the old locati=
on
> 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
> execute them. I am wondering what are the switches that makes the Windows
> build work. Can somebody help me with that? Thanks,
>
>
>
> Zhi