From: Zhi Han <zhi.han@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] OCaml configuration for sharpbangscripts
Date: Tue, 22 Jan 2013 08:51:16 -0500 [thread overview]
Message-ID: <CABUhoU4PEBk1Jpex=6h5P9gZss7PhhcyndQH86RTWd0fA4jyjA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
Hi, OCaml experts
I was tweaking the configuration for 'sharpbangscripts' on a Debian linux
box. What I want to do is the disable the generation of sharp-bang line in
the ocaml bytecode. By setting the bit to false in makefile it seems to do
the trick. However, this change breaks ocamldebug.
Here is the output of using ocamldebug:
% ocamldebug hello.d.byte # It does not debug, instead just run the program
hello ocaml world!
If I invoke ocamlrun before ocamldebug, it does not recognize the third
argument.
% ocamlrun ocamldebug hello.d.byte
Objective Caml Debugger version 3.12.1
(ocd) r
Loading program... No bytecode file specified.
I suspect that the argument was lost in the call chain because this error
is from the ocamlrun invoked from ocamldebug. Could someone help to look
into it? Thanks.
--
---------------
Zhi Han
[-- Attachment #2: Type: text/html, Size: 1156 bytes --]
reply other threads:[~2013-01-22 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABUhoU4PEBk1Jpex=6h5P9gZss7PhhcyndQH86RTWd0fA4jyjA@mail.gmail.com' \
--to=zhi.han@gmail.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