From: Sven Luther <sven.luther@wanadoo.fr>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: skaller@users.sourceforge.net, caml-list@inria.fr
Subject: Re: [Caml-list] Caml on intel-OSX
Date: Tue, 14 Jun 2005 02:28:24 +0200 [thread overview]
Message-ID: <20050614002824.GA6458@pegasos> (raw)
In-Reply-To: <20050610.094151.133749660.garrigue@math.nagoya-u.ac.jp>
On Fri, Jun 10, 2005 at 09:41:51AM +0900, Jacques Garrigue wrote:
> From: John Skaller <skaller@users.sourceforge.net>
> > On Thu, 2005-06-09 at 18:20 +0200, padiolea@irisa.fr wrote:
> >
> > > > Lol! no, it is a simple question. Can I make a bytecode program
> > > > and just ship it an expect it to run? No. So what else is required?
> > >
> > > I guess that if your bytecode program require some external libraries,
> > > such as for instance if you do a "open Dbm" then you must
> > > have too this library.
> > > I think that ocamlrun only include code to handle the Pervasive
> > > library.
> >
> > The code uses only (a) the standard library (Hashtbl and so on),
> > (b) the Unix library, and (c) Bignums. Therefore the bytecode
> > only requires support to be found in the standard distribution.
> >
> > I have a suspicion that one needs to '-custom' link somehow,
> > to make a suitable single bytecode interpreter. The desire
> > here is to *avoid* building Ocaml from source on the
> > target platform, instead to use pre-built binaries,
> > or, at worst, build these binaries from source,
> > excluding the full Ocaml toolkit -- the compiler isn't
> > required since the program is already compiled
> > to bytecode.
>
> In theory, it should be enough to have ocamlrun, and the dlls in
> stublibs.
> The an ocaml bytecode executable, linked _without_ -custom, could be
> executed as:
> $ setenv CAML_LD_LIBRARY_PATH /path/to/stublibs
> $ ocamlrun myprogram
> (Of course you need everything to be compiled from the same ocaml
> distribution.)
>
> The problem is that there is no support to compile only bits and
> pieces of the ocaml distribution. And there is little point to do
Works fine with a binary distribution like debian though, we ship the ocamlrun
and sublibs separatedly, and only those packages are needed to run a bytecode
package using them.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-06-14 0:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 5:33 John Skaller
2005-06-09 8:23 ` [Caml-list] " Agustín Valverde
2005-06-09 14:00 ` james woodyatt
2005-06-09 15:27 ` John Skaller
2005-06-09 16:20 ` padiolea
2005-06-09 22:51 ` John Skaller
2005-06-10 0:02 ` Jonathan Bryant
2005-06-10 2:55 ` John Skaller
2005-06-10 7:10 ` Florian Hars
2005-06-10 0:41 ` Jacques Garrigue
2005-06-10 1:57 ` John Skaller
2005-06-14 0:28 ` Sven Luther [this message]
2005-06-10 6:35 ` Stefano Zacchiroli
2005-06-10 9:07 ` John Skaller
2005-06-10 23:39 ` Jon Harrop
2005-06-11 18:39 ` John Skaller
2005-06-11 19:03 ` Jon Harrop
2005-06-12 6:58 ` John Skaller
2005-06-13 19:19 ` [Caml-list] AMD64 ocamlopt bug Xavier Leroy
2005-06-13 19:32 ` John Skaller
2005-06-13 20:18 ` Damien Doligez
2005-06-13 20:27 ` John Skaller
2005-06-13 21:01 ` Anil Madhavapeddy
2005-06-09 23:44 ` [Caml-list] Caml on intel-OSX Jonathan Bryant
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=20050614002824.GA6458@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=skaller@users.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).