caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Typing unmarshalling without marshalling types
Date: Thu, 29 Jun 2006 08:19:51 +1000	[thread overview]
Message-ID: <1151533191.5339.46.camel@rosella.wigram> (raw)
In-Reply-To: <ad8cfe7e0606281420m74c4bd4ayeb08d65d1494594a@mail.gmail.com>

On Thu, 2006-06-29 at 09:20 +1200, Jonathan Roewen wrote:
> > I used your shell script to build it, and mkcamlp4 doesn't want to
> > play nice (complains that odyl.cmo is not a bytecode object file).
> 
> Ohh, it's a shell script! And ocaml doesn't encode path info for
> ocamlc from the setting of prefix in the configure script.
> 
> I'm sure that's a quick fix from the ocaml team for the next release :-)

It isn't broken. The need to search the environment for the 
interpreter is mandated by the requirement scripts invoking
the names of ocaml executables are transparent with respect
to both:

(a) whether the code is bytecode or native code
(b) the machine it runs on

Hard coding the location of the interpreter breaks
requirement (b): it prevents shipping bytecode
from one machine to another because two people may
have installed the interpreter in different places
(indeed may be running different OS!)

If you KNOW you have bytecode you can invoke the
interpreter explicitly, in which case your shell language
already allows you to specify the location.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  reply	other threads:[~2006-06-28 22:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23  9:13 Michel Mauny
2006-06-27 18:11 ` [Caml-list] " Aleksey Nogin
2006-06-27 18:44   ` brogoff
2006-06-28 21:05 ` Jonathan Roewen
2006-06-28 21:20   ` Jonathan Roewen
2006-06-28 22:19     ` skaller [this message]
2006-06-28 22:27       ` Jonathan Roewen
2006-06-28 23:17         ` skaller

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=1151533191.5339.46.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=jonathan.roewen@gmail.com \
    /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).