From: Hugh Sasse <hgs@dmu.ac.uk>
To: caml-list@inria.fr
Subject: ocaml not native.
Date: Thu, 4 Mar 1999 16:31:10 +0000 (GMT) [thread overview]
Message-ID: <Pine.GSU.4.04.9903041603210.26819-100000@helios.dmu.ac.uk> (raw)
In htmlman/node9.html it says:
In script mode, the first line of the script is ignored if it starts with
#!. Thus, it is theoretically possible to
make the script itself executable and put as first line
#!/usr/local/bin/ocaml, thus calling the
toplevel system automatically when the script is run. However, ocaml
itself is a #! script on most
installations of Objective Caml, and Unix kernels usually do not handle
nested #! scripts.
ocamlopt builds successfully on my systems. Is there a reason why
the installation doesn't rebuild ocaml to be native code, when it can?
Is there a good reason not to attempt this myself?
(From/De http://babelfish.altavista.com/cgi-bin/translate? :
Dans htmlman/node9.html il indique:
**time-out** dans sequence type mode, premier ligne
sequence type ignorer si demarrer avec #!.
ainsi, theorique possible pour faire sequence type
soi-meme executable et mettre comme d'abord
ligne #!/usr/local/bin/ocaml, ainsi appeler toplevel
systeme automatique quand sequence type
exicuter. Cependant, l'ocaml lui-mjme est a #! siquence
type sur la plupart des installations de
Caml objectif, et les grains d'Unix habituellement ne
manipulent pas embonte #! des sequences type.
constructions d'ocamlopt avec succes sur mes systemes.
Y a-t-il une raison pour laquelle
l'installation ne reconstruit pas l'ocaml pour etre
code indigene, quand elle peut? Y a-t-il une
bonne raison de ne pas essayer ceci moi-meme?
)
Desole, mon Pine ne supportera pas des accents.
Thank you/merci,
Hugh
hgs@dmu.ac.uk
next reply other threads:[~1999-03-04 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-04 16:31 Hugh Sasse [this message]
1999-03-05 8:27 ` Fabrice Le Fessant
1999-03-05 14:12 ` Xavier Leroy
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=Pine.GSU.4.04.9903041603210.26819-100000@helios.dmu.ac.uk \
--to=hgs@dmu.ac.uk \
--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