From: Kristopher Micinski <krismicinski@gmail.com>
To: Zhi Han <Zhi.Han@mathworks.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Build OCaml on linux
Date: Sat, 22 Sep 2012 15:52:11 -0400 [thread overview]
Message-ID: <CAF1Sy-E4FKsDF_gHL3He-k+9WkW0mt1Cd_K1AFYGxNNQc_herw@mail.gmail.com> (raw)
In-Reply-To: <04644211E51C7E40BF64101089F97E4D0A7AE3DD@exmb-01-ah.ad.mathworks.com>
From 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 “bin/ocaml” 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 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
> execute them. I am wondering what are the switches that makes the Windows
> build work. Can somebody help me with that? Thanks,
>
>
>
> Zhi
next prev parent reply other threads:[~2012-09-22 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 19:50 Zhi Han
2012-09-22 19:52 ` Kristopher Micinski [this message]
[not found] ` <sympa.1348346044.7674.559@inria.fr>
2012-09-23 0:33 ` Edgar Friendly
2012-09-23 0:56 ` Wojciech Meyer
[not found] ` <04644211E51C7E40BF64101089F97E4D0A7B38C9@exmb-01-ah.ad.mathworks.com>
[not found] ` <CA+LkvyqbZxzY=Coj7v_XnkSBDyN8wGuQP9ZB41bCBHqsE6XfcQ@mail.gmail.com>
2012-09-25 0:36 ` Francois Berenger
2012-09-25 9:25 ` Fabrice Le Fessant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF1Sy-E4FKsDF_gHL3He-k+9WkW0mt1Cd_K1AFYGxNNQc_herw@mail.gmail.com \
--to=krismicinski@gmail.com \
--cc=Zhi.Han@mathworks.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox